Jump to content

Dave Martin

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dave Martin

  • Rank
  1. Dave Martin

    Masking trouble in Agisoft Photoscan

    Crystal, I'm not in front of my PhotoScan workstation, but a couple of quick thoughts: There are several options for masks, one of which is a separate mask for each image, in which case all you do is select the folder containing the masks - and the symptoms sound like possibly that's the route you're currently going down. I'm not sure if you have visited it already, but - especially as the issue isn't particularly subject-matter specific - I'm sure you would find it worthwhile to visit the dedicated PhotoScan forum operated by Agisoft themselves, where there's support from Agisoft staff and fellow users http://www.agisoft.com/forum/index.php?board=7.0 Also, on the Agisoft forum there is info on new masking methods (single image, volumetric...) which have been introduced in recent versions of PhotoScan. Dave
  2. Thanks Carla, yes understand can create a grouping for the dome, and apologies if I didn't make question clear. The point was that the dome structure is (relatively) invariant, so rather than have to associate pictures of the dome or rig with every image set taken with the dome, the 'normalised' solution would be to associate the pictures with the equipment. Similar might apply to, say, a photogrammetry turntable arrangement which was used repeatedly. Dave
  3. Thanks Erich, Have just tried that and, exactly as you say, ticking '[ ] Show associated?' does allow an operator to be added with another role. I would observe/suggest: 1) Not sure if it might be better either completely without the need to tick that box, or reverse the default / pre-tick the box. It certainly isn't obvious (until you know how!) 2) As you say, once that box is ticked, not only can you associate multiple roles, but you can add several instances of the same actor/operator with exactly the same role. Would strongly suggest that is not a valid result, so basic validation when associating an operator with an image set would be to present only those roles which they don't have already - so adding a completely new operator would in effect offer all roles; adding an operator for a second or subsequent time would offer a reduced set of roles (NOT IN ...) Dave
  4. DLN:CC Beta – software version 1.0.3 (build 26 Apr 2018 15:55:31) / DB version 2.2.3 First few observations / comments: Needs Regionalisation, in particular dates – looking at examples logged today (4 June 2018) it looks like 6 April 2018 (6-4-2018). If the system can’t/won’t reference the users’ locale, or maybe even as a ‘better’ fix, suggest that the date format, when displayed at least, is dd-mmm-yyyy so it shows 7-Feb-2018 etc which is then un-ambiguous world-wide. Registering an RTI image set has various string (Egyptian, not computer!)-related prompts. Might I suggest there’s a tick-box/radio-button or similar to indicate string or dome? Talking of domes, I can see how one would create an entry for a dome in the equipment register. Domes are rarely off-the-shelf and thinking of how one could/would document a dome, I wonder if the ability to associate photographs with project setups could usefully be extended to allow one or more photos of a piece of equipment (e.g. a dome type rig) to be associated with that equipment entry to save having to re-associate them with every group or set of images acquired using the same rig. In documenting an Image Set, it allows Operators to be associated, and to specify their role. However, it only allows one role per operator. In real life there may well be multiple roles for an actor/operator (e.g. image acquisition, computer processing). Could ‘fudge’ this by creating hybrid roles (e.g. 'photographer / computer operator'), or having schizophrenic clones of the same operator (‘Dave Martin – photographer’, ‘Dave Martin – computer operator’) but that is de-normalised and doesn’t reflect reality; so multiple roles are needed. Dave
  5. Trying to use DLN:Inspector with a DLN database (the sample database which installs with DLN:CC). The 'Project' at the top of the DLN:Inspector GUI does allow you to select a project; but the drop-down 'Group' to select image groups drop-down/combo is always empty so cannot get any further. Same if run DLN:Inspector RTI or PG. The DLN database has both the LACMA tests (RTI and PG) and some of my own initial tests in as well. None of them are accessible from DLN:Inspector (also, unlike DLN:CC, there's no 'About' which allows one to report more detailed version/build info, only the 'Version 1.0 Beta' in the title bar of the application)
  6. UPDATE: Have found a short-term work-around. I guess that there is a password embedded in the DLN applications, and if DLN:CC starts it must have the correct password. I noticed that on the DLN:CC Admin menu there was a 'Run script' option, so I first of all tried running the 'createpg.sql' script from DLN:CC - the script started OK, but then failed because the three sub-scripts that created the sequences, tables and then inserted the ref data only had relative paths when called from within 'createpg.sql'. So, I was going to modify a copy of 'createpg.sql' to embed the paths, but instead from within DLN:CC which was logged in to the database, I just ran the 'createsequence.sql', then 'createtable.sql' and finally 'insertlookupdata.sql' - all of which ran OK to completion. I can now start DLN:Inspector and connect to the DLN database. Dave
  7. Hi Carla, Have tried to install DLN:Inspector. Once I found out how to get DLN:CC to start (separate thread in DLN:CC section) I tried to start DLN:Inspector again and it came up with the first message shown below that the database had not been update for DLN:Inspector and to see the documentation for instructions. Checked online and in the installed program groups and could not spot the documentation. In the end I started DLN:Inspector 'without the DLN' and then, by clicking [Help] it opened the PDF. I then followed the instructions (which I guess are OK for beta testing but possibly not ideal for end-users long term) but, when the update is run, it fails with the message shown in the second screenshot. Dave
  8. UPDATE: - I had a look at/for the (not) installed database, then repeated the installation, and I've got it working now. I think problem when application was trying to connect to the database was not so much 'no password' as in fact 'no database'! The installer's default option under 'DLNCC Database' is 'Upgrade existing database'. If there is no database to install, it silently skips that stage. For first install, manually changing the option to 'New database, replacing the existing' seems to rectify the situation. This also removes the complaint when DLN:Inspector starts) Iain - suggest you try re-installing and tick the 'New database' option and see if that helps. I think / would suggest: the installer script needs to be 'cleverer' so if no database installed it will install skeleton one, or at least prompt the user; or at least the database option text in the installer screen above needs extra (like the PostgresSQL) so it maybe says 'New database, replacing the existing (check if first installation)' or at least some pre-install info/advice for the user . Dave
  9. Carla - similar (I think) question to IainS. When starting DLN:CC, it attempts to connect to the database - it pops up a database login (first pic), username defaults to 'postgres' with an option of two databases to connect to ('cpt_db' and 'cpt_db_v2.1'). Default password is blank, but there must be a password set as can't get beyond this point. Edit: I guess because DLN:CC hasn't got beyond this stage, DLN:Inspector complains at startup as well (second pic) Dave
  10. Dave Martin

    Initial view bookmark?

    Thanks Carla, I had suspected that ability was not in there yet. Is there a suggestion list anywhere for possible features in the RTI Viewer? - if so, I'd like to add this feature to that list. Dave
  11. Dave Martin

    Initial view bookmark?

    Is there any way to specify in a model that a particular bookmark should be activated when the viewer opens the model? The 'high noon' default can be less than ideal for first view, especially for a novice viewer. Rather than trying to coach the user to go down and open specific a bookmark, it would be great if one could specify, rather than 'NONE', a bookmark (with all its power) which would be activated as soon as the model is loaded (broadly similar to the way one can set the 'initial view' for a PDF). Dave