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.


Topics - mskancke

Pages: [1]
1
General / Yaw, pitch, roll not loading as reference
« on: July 06, 2016, 01:15:03 PM »
Hi

I have a dataset collected with a DJI Phantom 3 Pro and Pix4Dcapture app.

I loaded the photos into PS and lat/long is automatically inserted since its embedded in the exif data.
I have cleaned up the log from Pix4D which contains yaw, pitch and roll.
Created a new txt file which contains camera name and the orientation data.

When I try to import the orientation, I mess around with the column numbers to match the data in in the txt file.

Click OK, and no data is imported.
The existing lat/long is still there, but nothing added to yaw, pitch or roll

Is it not possible to do this task, or am I doing something wrong?

Dataset and logfile can be sent if needed, it ain't big since this is a test run..

2
General / Alligning photos takes ages
« on: July 03, 2015, 10:39:46 AM »
Hi

Hopefully not everyone has started their summer vacation yet.

I havent been working with photoscan for a while, but got a task to make a simple Georeferenced Orthophoto.

I fired up the drone and took around 800 photos of the area needed.


Ive started the allignment process, but it says its gonna take over 7 hours (its already been working for 24 hours)


Ive done this type of assignments before, with around the same amount of photos, but it never took more than 1 hour ish to allign the photos.


Im not working from my usuall station (its being repaired), so I took it into consideration when I gave the customer a timeframe, but I never thought it would take this long.

Im on a I7 gen 4 processor, so I really dont understand why its taking so long.
Taskmanager lists photoscan to be using 90-100% of processor capacity

Is it some bug in the new version?
Or have i missed something prior to starting the allignment?


BR

Marius Skancke

3
General / Need help to classify points
« on: September 19, 2014, 10:02:21 AM »
Hi

First of all, let me appologize, and say thanks in advance for any helpful tip. I am still pretty new to Photoscan.


We have been out with our Drone, and have taken pictures of a small quarry.
Our task is to produce a high quality georeferenced orthophoto, a detailed map with contour lines and do a mass calculation of remaining mass in the quarry.

The Orthophoto is fine, but the contour lines and mass prosjection is what I'm having trouble with.

The reason for this is the trees that are on top of the hill behind the quarry. They are generating too much fuzz, and makes the contour line software super confused.

Its the same with the mass calculation software, it includes the trees, which makes the projection accuracy low.

I have tried to classify points, but the result becomes even worse regarding the trees.

So if anyone have done a similar job, please share some tips, and I will be super gratefull.

Attaced is a screenshot of my classifications. (Please remember, im still pretty new to Photoscan)




4
General / Not enough memory
« on: September 05, 2014, 11:40:27 AM »
Hi.

Im hoping you can point out what I need to upgrade on my computer.

I have started the build dense cloud process on a job which contains 356 pictures/cameras of 4928x3264 uncompressed TIF's. All pictures is shot by our drone.
Dense cloud settings are High quality, and agressive depth filtering.

I've tried twich and both times the job has failed due to not enough memory, but at different intervals.

In console it says:
[GPU] estimating 652x1883x128 disparity using 652x942x32f tiles, offset 0
timings: rectify: 0.118 disparity: 0.258 borders: 0.023 filter: 0.039 fill: 0
[GPU] estimating 813x2251x160 disparity using 813x751x32f tiles, offset 0
timings: rectify: 0.651 disparity: 0.742 borders: 0.066 filter: 0.066 fill: 0
Error: bad allocation
finished depth reconstruction in 2140.63 seconds
Device 1 performance: 362.593 million samples/sec (GeForce GTX 770)
Device 2 performance: 363.933 million samples/sec (GeForce GTX 770)
Total performance: 726.526 million samples/sec
Error: bad allocation
Finished processing in 2304.95 sec (exit code -1)


Some key specs about my computer

Intel I7 4770K
16GB 1600Mhz DDR3 RAM
2GB Geforce GTX770
Windows 7 Pro


My questions are:
Is there any settings in Photoscan that can remove this problem?
I have done a similar job with success, although with fewer pictures (around 200), but according to the table found on your Tips and tricks section 16GB should be more than enough when using Hight field.

Is it the RAM that needs upgrading or the GPU?
Should I go for a GTX770 SLI config or just make my boss buy TITAN (or maybe SLI Titan)

BR

Marius Skancke

Pages: [1]