Jump to content

cdschroer

Administrators
  • Content Count

    459
  • Joined

  • Last visited

  • Days Won

    78

Everything posted by cdschroer

  1. Hi Fien - We have done some work to clean up the code a bit, so hopefully it will be more clear in the next version. The first one is a UUID for a label - I'm not sure of the context here. We do use UUID's throughout the system, and if you have them for certain things, like people and subjects, you can supply the ones you have, or the system will mint one for you. The second one I'm not sure, but it might be embedded binary for something like an image or a document (I mean an image of a setup - not the actual images that are part of your project). We have decided to handle this as separate files - so we will export them from the database and include them in the archive package that we will be producing - rather than having the binary inside the RDF. This was the behavior for the Beta though. Thanks for trying out the tools, and for your feedback! Carla
  2. hmm - I just downloaded and opened it just fine. It won't open when you click the link - but it should download. I'm using Acrobat and also tested it in preview on the Mac. Carla
  3. Tony - if you click on the tool/ configuration icon and click the button for "full size" that usually solves this particular problem. Sorry, I've been away from the forum a lot this summer - we'll just chalk it up to 2020 and leave it at that. Carla
  4. Wow - I think my notifications were somehow turned off - because I didn't get email about this message. And I so apologize for leaving you hanging. This is not a bug - and we are making this much simpler with the next version (I was just testing new software today) Essentially the issue is that in the Beta version you can only produce RDF for a group of image sets for Photogrammetry and for a single image set for RTI. We know this is confusing, so this is how we are fixing it: The idea is that you want to create RDF and Submission Information Packages (SIPs - new in the next version) for all of the images needed to produce a digital representation. So we are getting rid of the "groups" and instead introducing the concept of "Image Bundles." An Image bundle can be single set or multi set, depending on the technology. RTI is single set and photogrammetry is multi-set. Note that you can have a single image set in a photogrammetry image bundle - though you are allowed to have more. In RTI you can only have a single image set. It's at this image bundle level that it makes sense to do archiving and to export the metadata. We will also be providing reports for the Image bundle Bottom line is that in the Beta you have to export RDF from the group level for photogrammetry and from the image set level for RTI. This will be much cleaner in the new version, and we've integrated Inspector into the tools as well. We have massively redesigned the interface, and we are making it easier to add new "things" like people, stakeholders, etc - right when you want to use them. And lots of other updates too. It's a very active project right now. I think you will like the new tools. We will have scripts to update your database to support the new tools, since the data model has been changed to support the new features. So stay tuned - we hope to do a second Beta this fall. Carla
  5. Whoops - sorry for the delayed response. This summer has been a bit nutty - enough said. Do you get an error message, or does it just fail to detect the highlights? What platform (Mac or windows) you can also look in the .xml project log file that is created. That sometimes contains additional information about how far the process got and what might have failed. Carla
  6. Sorry, I'm a bit late to the party here - just catching up on posts, and I missed this before. In addition to the above suggestions, If you can see the whole surface you want to measure in one orthographic view - then you can make an orthomosaic and measure that. That is measuring along the surface, rather than point to point in a straight line. It doesn't work for everything, but for some situations it's a simple easy solution. Carla
  7. Hi Tom, Let me address a few things about the RTI software. First - both the RTIBuilder (with HSHFitter) and RTIViewer software are open source available upon request from us and under a GNU General Public License v3. This is noted in the software and the download page - and you only need to send email to info@c-h-i.org to receive it. We get 10-20 requests for the source code per year. Next - we are aware of the issues with the latest MacOS - Catalina and the requirement for 64bit software. We had some volunteer efforts underway to address this, which were set back with the insanity that 2020 has become. Just this week I received a test version of the HSHFitter that is 64 bit. If you want to test it, let me know. We'll release it once we've tried it out a bit. The PTMFitter is a bit trickier, because it's proprietary from HP, and none of the original folks who worked on it are there any more. We are working on a solution there, but it will take a bit longer. There is also a test version of 64bit RTIViewer for Mac - and it works fine for me (though I'm not running Catalina) and the person who tried it on Catalina couldn't get it to run. If you want to try that, again, let me know. Bottom line is that we do care about this software and know there are issues, but haven't had funding for software updates. We've put a small budget in a recent grant proposal that, if funded, should at least be able to get all the current software updated and running on the latest OS's and repackaged to get rid of the virus warning. We won't know until December if we will receive that funding. In the meantime, we hope to release these smaller pieces. There are a number of research labs working in this space. I don't know about the specific art scanner you link to, though Szymon Rusnkiewicz and team at Princeton have been doing similar things with modified flatbed scanners since 2007 - and have published some papers in this area such as this one: "A System for High-Volume Acquisition and Matching of Fresco Fragments: Reassembling Theran Wall Paintings" (with Benedict Brown, Corey Toler-Franklin, Diego Nehab, Michael Burns, David Dobkin, Andreas Vlachopoulos, Christos Doumas, and Tim Weyrich), ACM Transactions on Graphics (Proc. SIGGRAPH), 2008. We are interested in working to incorporate some of the most recent research in this area into usable tools for this community - and would like to do a proposal later this year to see if we can get it funded. We'll keep you posted if that happens. Thanks for your interest! Carla
  8. Hmm - I have it working on Windows 10 - just a regular install from our download in winter 2019. I haven't tried it recently. So sorry about all the problems. Carla
  9. Thanks Hembo! Turns out that RTiViewer won't run on Catalina either. Gianpaolo Palma from the Visual Computing Lab in Pisa is looking into recompiling it for 64 bit. He thinks it will be straight forward if we lose the functionality for the network viewing. That was really just an experiment in the current version, and I think there are better options for folks now - so losing that feature to get 64 bit seems like something we can live with. 2 different people are looking into 64 bit PTMFitter and HSHFitter. PTMFitter isn't open source, and we don't have the code. We do have the code for HSHFitter. Are the fitters the problem - or can you not run the RTiBuilder application? Please post any specific error messages you receive. Thanks - and I've just pinged the folks that were working on all these things to try to get an update. I'll let you know if there is a way for you to get involved. I appreciate the offer. Carla
  10. The first question is what platform are you on? If you are on Mac make sure that you install RTIBuilder somewhere on your system (i.e. drag it from the disk image (.dmg file) onto your hard drive) Most folks put it in Applications. If you run it from the disk image you can have problems like this. If this isn't the problem for you, then give a bit more info about your setup to help us figure it out. Carla
  11. HSHfitter was compiled as a 32 bit app on the Mac - and those aren't supported in Catalina. Someone is working on trying to solve this for the PTMFitter. The PTMFitter is turning out to be more work than initially thought, due to dependencies in the code. Note that it is NOT open source, and CHI does not have the code for it. I've asked someone to do this for HSHFitter - and I'll post when I have an answer as to whether they can do it, and when. We do have the code for HSHFitter and it is available under the GNU General Public License v3. Sorry for all the issues with this old software. Carla
  12. Thanks for jumping in Dave - I just checked it also - and it is downloading fine for me. I think your idea about it being quarantined by virus software makes the most sense. Carla
  13. I understand that PTMFitter is 32 bit, and therefore will not run in Catalina until we can create a 64bit version. We have had some discussions about that with various folks, because (as noted above) the PTMFitter is not open source code, and we at CHI do not have the code. We think we may have a solution - but I don't want to say for sure until we are sure. I just want to let you know that we have contacted folks who may be able to solve it. However, I'm not sure why RTIBuilder - which is a Java Application would not run, nor why HSHFitter wouldn't run. I just used the Go64 app and it says that the HSHFitter is also 32 bit. We do have the code for that one, so it should be easier to fix. I didn't get any warnings about RTIViewer. I have an older Mac and not running the latest OS. If anyone has tried ay of the tools on Catalina - please post what you have found about RTiViewer and RTiBuilder - other than the fitters, which we know are a problem. Carla
  14. Thanks for posting the RTI-dome.com - We're not familiar with them. It appears to be a small dome for insects and other very small subjects. Carla
  15. There are a lot of 32bit apps stil in use out there. Here's a quote from an article in Time magazine this week about how to check to see what 32bit apps you have on your system: "... if you’re dependent on a particular 32-bit app, it won’t work in macOS Catalina, as many Twitter users discovered after upgrading. Meanwhile, some popular apps, like Adobe Photoshop, appear to be suffering from temporary compatibility issues with Catalina, so it’s best to hold off on upgrading until a software patch resolves those problems. Want to see which of your apps are still 32-bit? On your Mac, hit the Apple menu, select About This Mac, and click System Report. In System Report, scroll down to Legacy Software, and take a look at all your 32-bit apps." Here's the full article: https://time.com/5696302/macos-catalina-upgrade/ I know this doesn't resolve the problem if RTI software no longer running - but I did want to point out that folks might want to be cautious about upgrading until they see the full impact - not just RTI software. Carla
  16. Thank you for letting us know about this. We can contact various folks to see what the simplest fix is for this issue. For the PTMFitter - that is HP software, and not open source. We do not have the source code for it - but I know some researchers who have it. Carla
  17. We run RTIBuilder successfully on a Windows 10 machine. We are mostly a Mac shop, so I'm not super familiar with the Windows environment, but I wanted to note that Windows 10 can successfully run RTIBuilder. The software is old, and we'd love to update it. We are a small independent nonprofit, and the initial work was paid for by a grant and some volunteer efforts. We'd love to get funding to update it, but selling individual copies isn't a way to get that done (especially since it is open source software, per the agreements of the funder and all parties involved in it's development). We still use RTI frequently, and think it is a very useful technique. It will take a new grant to create an updated version. Thanks to Dave for jumping in and asking for the details. Much appreciated! Carla
  18. There are some good ideas here. The easiest one to implement is adding a notes field. I'm not sure we can do the other ones in the current version because of time and budget constraints, but we'll talk it over. You can use the Notes field to store additional info - though it does have the drawback of not being as easy to find, and also not being mapped to the CRM, etc. Carla
  19. Have you looked at the WebRTIViewer? http://vcg.isti.cnr.it/rti/webviewer.php It's from the Visual Computing Lab in Pisa - and those folks have spent some time looking at compression and tiling and similar techniques for using big files over the internet. The project is open source. Contact info for Gianpaolo Palma is also on this page. He was the primary developer. They also support RTIs in the 3D Heritage Online Presenter (3DHOP) tool. It's from the same team. Carla
  20. Hi Dave - and thanks for the detailed notes! Actually you can link rights to both the subject AND to the images of the subject. I admit it isn't as clear in the interface as it should be, and we are fixing that. The idea is that the subject may still be in copyright, and that's an important thing to know. So subjects can have rights statements, including noting whether it is in copyright. For our imaging work, we generally care more about the rights in the images, and we can do that too. But even if my organization has the rights in the images, if they are images of an artwork that is in copyright, we would want to record that. Also remember that you don't have to use all of the fields and associations that are there. So, if you don't want to note a rights statement about a subject you don't have to. Another important note about rights statements is that they are a high level way of noting what kind of rights are intended, but they aren't an actual license. So for material that is in copyright, you need to be able to say who is the copyright holder, and what is the general license (if there is one) This also lets people know where to go if they need to get a license for something different. We were just discussing this mechanism this week, as we are planning major updates for the tools. We want to make it possible to set up the rights at the project level, so that all the imaging sets that are part of that project automatically get those rights. Then if you need to do something different for a specific set of images for say an RTI - you could override that. We are also looking at how to make this more clear in the interface, so you can see the rights (and other attributes) and where they are coming from. In other words, are you getting those rights from the project, or are they local to this particular RTI (or photogrammetry) set. And this brings me to a new concept we will be introducing: Image Bundles. An Image Bundle is all of the images that will be processed together of the same subject (remember that a subject can be a scene, not necessarily a single object). An Image Bundle can be a single-set image bundle, or a multi-set image bundle. That is determined based on the technology. So RTI image bundles are single set, and Photogrammetry image bundles are multi-set. We will get rid of "groups of image sets" (it's still in the data model - but the interface will be much cleaner) We are adding single-set image bundles for documentary image sets. And finally - related to your prior comments, we will be adding an image set type, that is user defined. So, if you have a Documentary photos technology type, you can create subtypes for HDR, or stratigraphy, or small finds, or whatever is useful to you in organizing and finding and labeling your image sets. Thank you so much for taking a deep look at the tools, and for taking the time to write up your experience, questions and suggestions. We have been using the tools more and more, and also presenting them to others, and have run into some of the same issues. Some of them are harder to solve than others, though we feel the whole system is getting better. Cheers! Carla
  21. Hi Dave - Thanks for the notes and for using the tool! We are adding an additional technique type for "documentary photos." That will be in the next version (we are working on it now). We are also discussing adding support for multi-spectral image sets. I think with a documentary photos technology type - you could support additional kinds of image sets, because the Inspector would do a very minimal check on the images, and you could add a description or note for which kind of thing it was. Maybe we should think about subtypes within documentary photos? We don't want to add the ability to make top level new techniques, because there are significant smarts built in about what these techniques mean for Inspector, as well as how the data is grouped and saved. Further there are customizations for the image sets around the technologies, such as string length and sphere size for RTI - and differences between image sets for photogrammetry. There would be no way to have these kinds of technology specific customization for user defined technology types. I'll note that we realize that the use of image sets and groups of image sets is confusing. We are adding a notion of an Image Bundle - which is the images of a subject or scene that will be processed together. For RTI that's a single image set. For photogrammetry that's a group of image sets. For the new documentary photos that would also be an image set. This way you can see all the image bundles within a project, etc. We are working on some additional reporting functionality. We'd love to get your thoughts about this kind of approach and whether it would meet the needs you see. Carla
  22. I agree generally with the advice listed here. We stay away from contrast curves. You can apply a white balance and an exposure compensation when needed, and this can be done for individual images or sets of images. The main thing when doing an exposure compensation is that you are trying to get a matching histogram across the images (not exactly, and will potentially vary for different parts of a subject) The point is that you can make some adjustments that will give you better photos, without applying contrast curves or sharpening. If you have heavily shadowed areas within a photo and some areas are bright, you can also bring up the shadowed area. This is essentially an exposure compensation applied only to the dark parts of an image. Don't go crazy with these modification though. As for the second part of your question, you absolutely can make new jpegs or tiffs from your RAW or DNG files with exposure changes. As long as they have the same name and are in the same location on your hard drive, (or you reset the path to point to them) Agisoft software will use those images for any operations after you replace them. We have done that to correct for lighting differences across an image set and to remove what Dave referred to as "boundary effects" or light and dark stripes or patches across a surface. This can occur for a variety of reasons including shooting something in the round outdoors where one side is in shadow and one side is in full sun. Also if the sun is going in and out of clouds you can have these issues. Ideally you would correct for that when you are shooting by adjusting shutter speed. Carla
  23. Please read this thread and see if it solves your problem: http://forums.culturalheritageimaging.org/topic/534-not-able-to-import-images/?tab=comments#comment-1692 Also note that you should post in the most relevant forum for your question - in this case, Processing RTI data. We'll move things to the FAQ if multiple people run into it. Carla
  24. The file on the HP site appears to be corrupted. I've uploaded a correct one to the FAQ forum post about file formats: Now both the RTI and PTM format specifications are available from this thread:
  25. The PTM format document on the HP website appears to be corrupted. I've uploaded it here. Note that you have to be logged in to the forums to access attached files. Carla PtmFormat12.pdf
×
×
  • Create New...