Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rossnixon

Pages: 1 ... 4 5 [6] 7
76
General / Re: Duration of photo alignment
« on: March 23, 2017, 01:17:31 AM »
If there is no longitude/latitude data in the images, that could be a reason for it taking a long time.

I have processed 2129 geo-tagged images with an i5 @ 4.2GHz, 16GB RAM, onboard video. Initial alignment may have taken less than 12 hours (I don't recall exactly). I used 20,000 key points & 4,000 tie points

78
As far as I know, just the following:
• focal length
• absolute pixel size on sensor
• longitude & latitude (just for initial alignment; then use GCPs)

79
Python and Java API / Re: 'null' value on exportOrthomosaic
« on: March 07, 2017, 12:26:00 PM »
Only a choice of black or white? I prefer a magenta - which happens to be a colour which is never found in my orthophotos.

80
Feature Requests / Tracking RAM percent free
« on: February 24, 2017, 05:00:01 AM »
It would be useful if Photoscan could report how much RAM was being used at various stages of processing.
If this was in the LOG file every few minutes, we could see how close we came to the limit.

For example, I was doing Color Correction over 2100 photos, and ran out of RAM.
I did not know that this was a RAM-intensive thing. I closed all other programs and tried again. Being curious, I started Task Manager to see what it was using and saw RAM usage was 91%. This time the color correction completed successfully.

81
Python and Java API / Re: Split In Chunks - failed
« on: February 24, 2017, 12:14:46 AM »
Low Quality has worked. Got a complete Dense Cloud, Mesh, Merged chunk.
- Tie Points: 1,054,000
- Dense Cloud: 85,600,000 points, Low quality
- 3D Model 17,000,000 faces

I'm still uncertain if my 16GB of RAM was causing the 'Bad Allocation', or whether it was my C: drive filling up (8GB free). Does Photoscan use C: during the processing?
My %temp% is currently D: (135GB free) which I believe is sufficient.

82
Python and Java API / Re: Split In Chunks - failed
« on: February 23, 2017, 11:45:46 AM »
I used the standard supplied script with the Dense Cloud set to Medium Quality.
I'm trying again now with it set to Low Quality and with 2x3 chunks. I will be back at work in 12 hours to check the result.

83
Python and Java API / Split In Chunks - failed
« on: February 23, 2017, 12:26:45 AM »
I'm using the Split In Chunks script, but am getting "bad allocation" after the last chunk is processed.
- The previous attempt (3x2) finished with just the final chunk having a Dense Cloud, and the other chunks have disappeared.
- I increased the number of chunks (3x5) but get a similar result. No Dense Cloud as the last chunk was in an empty zone.

LOG file:
2017-02-23 04:47:16 Merging chunks...
2017-02-23 04:47:16 Error: Empty surface '//If this refers to the final chunk, there were no cameras there.
2017-02-23 04:59:55 Finished processing in 758.664 sec (exit code 0)
2017-02-23 04:59:55 Script finished
2017-02-23 04:59:55 Error: bad allocation

Is "bad allocation" always a lack of memory?
Or could it be lack of disk space?
At what stage is the failure occurring - is it the 'Merge Back'?

The script has three options
- Build Dense Cloud
- Build Mesh
- Merge Back
    Should I try just the first two options to see if the Dense Clouds and Meshes are retained?
    Then is there a way to do only the Merge Back?
(Screenshot attached)

84
General / 32-bit TIFF output?
« on: February 22, 2017, 12:24:35 AM »
I created some tiles from an orthophoto, and noticed they appear to be 32-bit TIFFs, so I resaved as 24-bit which made them considerably smaller.

Does anyone know what use 32-bit TIFFs are?
Can I specify 24-bit ( 8 bits per channel ) in Photoscan for the output?

85
Bug Reports / Re: [Build dense cloud] Error: bad allocation
« on: February 15, 2017, 12:46:55 PM »
For very, very large files (unlimited size), you could use https://infinit.io/
Of course you would compress the files to a ZIP or RAR file first.
Infinit.io is closing down on 31 March though. I just checked and the program is still available for download.

86
Python and Java API / Re: Split_In_Chunks - can I restart part way through?
« on: February 02, 2017, 03:06:20 AM »
I repeated the script run overnight, after killing a few more background programs and services.
The console's last two entries were:
  2017-02-02 07:55:47 Script finished
  2017-02-02 07:55:47 Error: bad allocation

Looking around, I see I do have a Dense Cloud.
I also have two chunks: One of 4110 cameras. One of 0 cameras, which I deleted.
In my 2 x 5 split, it looked like one rectangle would have nothing in it. Could that have been the cause of the "bad allocation" message?

Then I generated a Mesh.
Then I generated an Orthophoto with default resolution (1.04m). This was successful.
The images are closer to 0.2m resolution, so now I'm trying that.
UPDATE: "Can't write pyramid data".
Trying again now with much more free HDD space.

87
Python and Java API / Re: Split_In_Chunks - can I restart part way through?
« on: February 01, 2017, 04:45:14 AM »
Here is the full log. https://dl.dropboxusercontent.com/u/20604246/Agisoft_Log_31st.zip

Under View, I only have Point Cloud as an option.
Is that where I should be able to see Dense Cloud & Mesh?

If I repeat the script, I now know to look for a hidden CMD window, or perhaps View Console, before saving and closing Photoscan.

88
Python and Java API / Split_In_Chunks - can I restart part way through?
« on: February 01, 2017, 12:34:01 AM »
I ran the Split_In_Chunks.py script.
I specified a 2 x 5 grid so that I would have fewer than 600 photos per chunk. (I have 16GB of RAM).

This took over 13 hours, but I think it has failed because:
1. I think I saw a console window with error messages flash past after I saved then closed Photoscan.
    Are those Python messages logged anywhere?
2. Build Orthomosaic is greyed out (not available).

I can't see any errors in the Agisoft log file, which finished like this:
2017-01-31 23:17:44 Merging chunks...
2017-01-31 23:27:47 Finished processing in 602.982 sec (exit code 1)
2017-01-31 23:27:47 Script finished

Can I restart the script part way through?
I have some large files that may still be good:
- dense_cloud.oc3   3.0GB
- model.zip   933MB
- point_cloud.zip   310MB


89
Well, they are gone now, whatever they were, after some more 'Optimize Cameras'. Also I may have close and re-opened Photoscan. Can't remember exact sequence.

90
General / Re: Editing .Raw
« on: January 30, 2017, 05:59:16 AM »
The PNG specification does not include a standard for embedding EXIF image data from sources such as digital cameras. Instead, PNG has various dedicated ancillary chunks for storing the metadata that other file formats (such as JPEG) would typically store in Exif format. https://en.wikipedia.org/wiki/Portable_Network_Graphics

Saving the images to PNG has lost the EXIF data, including GPS longitudes and latitudes.

Pages: 1 ... 4 5 [6] 7