Jump to content

leszekp

Members
  • Content Count

    96
  • Joined

  • Last visited

  • Days Won

    31

Everything posted by leszekp

  1. You can in principle reconstruct a 3D surface using normals calculated from the PTM and RTI files. Here's a link to a paper where they did that (see Figure 11): http://palaeo-electronica.org/2002_1/fossils/issue1_02.htm I don't believe the software to do this has been released, so you'd have to write it yourself.
  2. I've played around with some of the open source / freeware alternatives to Adobe's LightRoom (RawTherapee, RawHide, Photivo), but never been happy with any of them. Lifehacker recently posted about LightZone, a former commercial package that is now open source freeware: http://www.lightzoneproject.org/ Handles raw files and color conversions, and I find the interface much easier to work with.
  3. I emailed one of the authors asking about software availability, but no reply to date. The technique appears to use fairly-straightforward algorithms - maybe something that could be added to a future version of RTIBuilder/Viewer? Thanks for the references. I did see the McDonald paper, but AFAIK that software hasn't been made publicly available, either; would love to try it out. Writing a comparable program for triplets is a bit beyond my current abilities, so I'll start out with normals from the full dataset, which is a lot easier. XShade looks interesting - will have to give that a try with some of my 3D models.
  4. Hi Marlin, Just want to make clear I'm not directly associated with the work in this paper, found it recently in an online search. I'm interested in fossils, and have shot a few with RTI, but that's strictly avocational. The primary use of my custom-built RTI dome has been for archaeological artifacts, mainly projectile points and other lithics, but a few other types as well; whitening is often used on lithic tools to enhance surface details. I've attached a pair of photos of one item, a Clovis point from Arizona, an original digital photo and an enhanced RTI image that's comparable to what you might get using whitening. I'm presenting on the technique and initial results next week at the Arizona Archaeological Council 2013 Conference in Mesa, AZ (and yes, CHI will get a shout-out). I've been working with photogrammetry for a while now, documenting archaeological digs/features, and medium-sized artifacts. The lithics I've been shooting with RTI are small (1-3 inches typical) and usually have poor contrast and very limited surface topography, so I've considered them poor candidates for photogrammetry. Just tried a test run on one of them, and sure enough, the resulting mesh is very low quality; may try some more experiments in the future if I can find the time. I am working on a SciLab program to take the RTI photo dataset and do photometric stereo analysis on it; this may provide superior normals images, but also can in principle generate high-res surface topography meshes. Best, Leszek
  5. Virtual whitening of fossils using polynomial texture mapping http://palaeo-electronica.org/content/2013/465-virtual-whitening-of-fossils I get comparable results using image enhancement, but this looks like it might be a faster and easier way.
  6. Just a brief update. Intel states on the following page that drivers for their graphics chipsets obtained directly from Windows Update or the OEM may not support OpenGL: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20046 And suggests downloading drivers for these chipsets directly from Intel for full OpenGL support. They also suggest going into the control panel to check the settings: http://www.intel.com/support/graphics/sb/CS-030506.htm We tried that with the problematical laptop we've been strugglng with (which uses a 945 Intel graphics chipset), but it didn't solve the problem. However, it might work for other Intel chipsets, or for other computers with the 945 chipset. Worth a shot, in any case.
  7. We're going to try updating graphics drivers for these systems again; first attempts failed, as Windows said that they were already up to date. But if it's the Intel integrated graphics that's the problem, this may be a futile endeavour, as both systems use that. And they're both laptops, so they can't be upgraded.
  8. The Smithsonian has been doing some work with early photographs and RTI: http://www.si.edu/mci/EarlyPhotography/rti.html http://www.si.edu/MCIImagingStudio/daguerreotype_presentation_movie
  9. Thanks for the reply. It's just weird that the program worked on his main computer before, but no longer doesn't. We'll take a look at his install history, to see if we can spot any potential problem programs that were installed after RTIViewer.
  10. I sent a few PTM files to a friend, and he reported that when he opened the files in the main RTIViewer window was filled with solid red - no view of the PTM image. The image in the lower right hand corner shows up correctly, and if you save a snapshot, the view is also correct. He also sees the same problem with the HP PTMViewer program. The original problem was on a Windows 7 system, but we've duplicated it on two Windows XP systems of his as well. What's more, PTM files that he was able to view successfully in the past now also have the same problem. His graphics drivers and Java version are fully up to date. I've tested these files on three of my Windows systems, and they work perfectly on all of them. I'm stumped - any ideas?
  11. I've been trying to use an older release of RawTherapee on my Windows system, but it crashes on a regular basis. There is a more recent release that is available for Mac and Linux, but hasn't been ported to Windows yet. Just starting to experiment with RawHide to see if it will work any better.
  12. Forgot - this works by default only in Vista and 7 (possible Windows 8, though I will avoid that abomination till my dying day). Before those, I set up Windows XP to allow that - it's a simple registry edit. http://www.howtogeek.com/howto/windows/add-the-command-prompt-to-the-windows-explorer-right-click-menu/
  13. Yeah, this one drove me crazy for a while as well. I think it's been posted on the forum already, but a simple way to rename all files in a Windows folder with a new extension is: 1. Right-click on the folder with the Shift key depressed, and choose "Open command window here". 2. In the command window, type "ren *,JPG *.jpg". Done.
  14. There are two right-click options in PTMViewer that I can't find any documentation on. The first is "Output Depth Values"; running this gives an error message indicating that the program can't find a .cam camera file (not surprising, since there is none). The second is "Output Source Images As Volume", which gives an error message indicating that it can't find the .lp file (which is odd, since the file it can't find is definitely there). I've looked long and hard on the Web for any information on these, without success. Anyone have any info/links on these options?
  15. Thanks, Carla. Sorry for the delay in responding, but my dome showed up on my doorstep last week, and I've been busy finishing assembly on the system and testing it (It works! Really well!). Not a critical issue for me - I've written a program that will take a list of all the photos in a directory and combine that with the LP calibration data from my dome to generate an LP file, then create PTM/RTI files directly using the fitters. So while it would be great to have this working in RTIBuilder, it's not a showstopper for me. Let me know if there's any more information you need.
  16. Well, I thought the LP option was working, but there's a bug in it. Here's the first 4 lines of my original LP file: 21 C:\Users\Leszek\Desktop\test_PTM_Images\No_space_PTM_Project_Folder\jpeg-exports\No_space_01.jpg 0.95020884 -0.0991746 0.29541084 C:\Users\Leszek\Desktop\test_PTM_Images\No_space_PTM_Project_Folder\jpeg-exports\No_space_02.jpg 0.7782148 -0.13303308 0.6137458 C:\Users\Leszek\Desktop\test_PTM_Images\No_space_PTM_Project_Folder\jpeg-exports\No_space_03.jpg 0.6559495 -0.16346425 0.7368919 And here's the first four lines from the LP file in the assembly-files folder, after processing it with the LP File option in RTIBuilder: 21 C:\Users\Leszek\Desktop\test_PTM_Images\No_space_PTM_Project_Folder\jpeg-exports\No_space_01.jpg 0.29541084 -0.0991746 0.95020884 C:\Users\Leszek\Desktop\test_PTM_Images\No_space_PTM_Project_Folder\jpeg-exports\No_space_02.jpg 0.6137458 -0.13303308 0.7782148 C:\Users\Leszek\Desktop\test_PTM_Images\No_space_PTM_Project_Folder\jpeg-exports\No_space_03.jpg 0.7368919 -0.16346425 0.6559495 The program is swapping the first and last angle parameter for every photo; hilarity ensues in the final PTM as a result. Same thing happens for both PTM and HSH fitting. Data gets processed correctly if I run PTMFitter and HSHFitter from the command line with the correct LP file.
  17. Okay, so I've actually written a program that takes an RTI photo sequence, renames the photo files so that the last digits are sequential (e.g. test_01.jpg, test_02.jpg, test_03.jpg etc.), then creates an LP file with exactly those filenames and the correct file path for every file. I then tried loading that into RTIBuilder with the following results: 1. LP File (PTMFitter): Loads in the images correctly after I select the Light Position File and the Project Folder. When I get to the final screen where the PTMfitter is executed, the image screen on the left is black, so I can't crop the image. When I "Execute", I get an "Unknown Error" popup. Looking in the PTMFitter Output Information, I can see that RTIBuilder is telling PTMFitter that the images are in a "jpeg-exports" subfolder of the Project Folder, even though the lp file specified their exact folder location. However, if I manually copy the image files into a "jpeg-exports" subfolder of the Project Folder, an image shows up at left that can be cropped, and a PTM file is generated successfully after pressing Execute. 2. LP File (HSHFitter): Loads in the images correctly after I select the Light Position File and the Project Folder. When I get to the final screen where the HSHfitter is executed, the image screen on the left is black, so I can't crop the images. When I "Execute", I get a popup window titled "JPEG Library Error", and the message "Improper call to JPEG library in state 200". No file is created. This is followed by an "Unknown Error Detected" popup. In the HSHfitter Output Information window, it says: Sample Image -> W: 3539140 H: 3551192 Channels: 1095519311 Parameters read successfully HSH matrix : Rows= 4 Columns=42 Number of Threads : 8 But if I manually create a jpeg-exports folder and copy the images there, as with the PTMFitter, I now see an image in the left of the "Execute" window which can be cropped, and an RTI file is generated successfully after pressing Execute. I think it might make things less confusing if the program: - Specifies the original image location to PTMFitter and HSHFitter, rather than using "jpeg-exports" subfolder of the project folder, or - Gives a warning message about how the images need to be in the jpeg-exports subfolder of the Project Folder right from the start, or - Copies the images from their original location into a "jpeg-exports" folder in the Project Folder, so that the fitters will find them there, and lets the user know it's done that. 3. Neither of the LP Dome Fitter options (HSH or PTM) worked at all. I specify the lp file, the Project Folder, and the folder that contained the images, and nothing happens - no images get loaded, no error message, nothing. This is true when I specify the original image locations, and also when I specify "jpeg-exports" as the image location after I've copied the image files into that subfolder of the Project Folder. You mentioned that you would be eliminating the LP File option in a future version. Given that the LP File options seem to be the only ones working right now, please don't do that!
  18. Yes, images will be captured to the card, so I'll have to manage it another way - either with a program or a spreadsheet.
  19. Yes, absolutely makes sense, thanks; will give it a try. I'm wondering whether it might be easier for me to: 1. Put all the images from a single sequence into one folder; 2. Write a program that reads in all the filenames in the correct sequence, matches them to the correct light position from the "template" file, then writes an lp file with the correct image names/path. That way, I don't have to worry about changing the last digits in the image's filename to match the "template" sequence. When I'm ready in a month or so, I'll try it and let you know which I prefer.
  20. Thanks, Carla. I'm looking to put together a dome, and wanted to play around with an LP file and associated photo set created using highlight detection to get a feeling for how to process photos taken in the dome. I thought I had the photo file paths correct, but reading your response, I'm guessing the paths probably had a mistake somewhere, and that's why I kept getting messages about all the images not being found. I plan to create a "template" LP file using highlight detection, then modify it to incorporate the full names and paths of the dome artifact photos in proper sequence to match the LP positions.
  21. How do you use the Dome LP File and LP file Operation Sequences in RTIbuilder? I assume that they're to allow you the option to load in images for which you already have an LP file, and don't need to use the highlight detection features. But there's nothing in the manual about them, and I've been unable to figure out through experimentation how to get them to work.
×
×
  • Create New...