1
Bug Reports / Re: cannot run last PhotoScan version 1.0.0.1795 in ubuntu 10.04 LTS
« on: January 21, 2014, 05:58:33 PM »
Thank you Alexey,
this was indeed the problem!
this was indeed the problem!
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.
2
Bug Reports / Re: cannot run last PhotoScan version 1.0.0.1795 in ubuntu 10.04 LTS
« on: January 21, 2014, 05:09:15 PM »
Hello Alexey,
sorry for my late respond,
after typing ./photoscan.sh in the proper folder (i.e. the folder containing all the files extracted from photoscan-pro_1_0_0_amd64.tar.gz), the following appears on the terminal:
./photoscan.sh: 12: /media/sda3/SHARED/software/photoscan-pro/linux/stable-version-1.0.0-build: not found
regards,
Jan
sorry for my late respond,
after typing ./photoscan.sh in the proper folder (i.e. the folder containing all the files extracted from photoscan-pro_1_0_0_amd64.tar.gz), the following appears on the terminal:
./photoscan.sh: 12: /media/sda3/SHARED/software/photoscan-pro/linux/stable-version-1.0.0-build: not found
regards,
Jan
3
Bug Reports / completely black texture
« on: January 10, 2014, 03:57:42 PM »
Hello,
I just made a mesh of 1000 photos (non of them are black), and the topography seems ok, but after building texture,
the produced texture is completely black...
I retried several times, but no improvement... Does anybody knows how to deal with this?
kind regards,
Jan
I just made a mesh of 1000 photos (non of them are black), and the topography seems ok, but after building texture,
the produced texture is completely black...
I retried several times, but no improvement... Does anybody knows how to deal with this?
kind regards,
Jan
4
General / too large marker coordinate errors
« on: January 10, 2014, 01:47:51 PM »
Hi,
I'm working on a large project (5000 photos). I want to make 5 chunks of 1000 photos each, and merge these chunks later on. There are no camera coordinates, but I have 9 GCPs.
Thus far I aligned, made a mesh and optimized a first chunk. 4 GCPs are visible on this chunk, and the GCP error coordinates are very good (errors are less than 0.005 m, while the chunk itself is bigger than 100 m in both dimesions).
Now, for the second chunk, only 2 GCPs are visible, but these 2 GCPs are both also visible on the first chunk. The strange thing is that for the second chunk, after giving in the marker coordinates in the ground control pane, the GCP erros are huge (> 100 m for 1 of the 2 markers). How come this is possible as the marker errors are tiny in the first chunk (for the same two markers)?
regards,
Jan
I'm working on a large project (5000 photos). I want to make 5 chunks of 1000 photos each, and merge these chunks later on. There are no camera coordinates, but I have 9 GCPs.
Thus far I aligned, made a mesh and optimized a first chunk. 4 GCPs are visible on this chunk, and the GCP error coordinates are very good (errors are less than 0.005 m, while the chunk itself is bigger than 100 m in both dimesions).
Now, for the second chunk, only 2 GCPs are visible, but these 2 GCPs are both also visible on the first chunk. The strange thing is that for the second chunk, after giving in the marker coordinates in the ground control pane, the GCP erros are huge (> 100 m for 1 of the 2 markers). How come this is possible as the marker errors are tiny in the first chunk (for the same two markers)?
regards,
Jan
5
General / checking all cameras at once in ground control pane
« on: January 10, 2014, 11:33:53 AM »
hi,
I'm using ps 1.0.0.1795 (64 bit) for the moment in win7.
I want to check all cameras in the ground control pane, but it seems not possible.
I tried to first select all cameras (ctrl A), then right click mouse, and press 'check'
but this doesn't work.
Is there another way as checking each camera manually can be a lot of work with many photo's...
kind regards,
Jan
I'm using ps 1.0.0.1795 (64 bit) for the moment in win7.
I want to check all cameras in the ground control pane, but it seems not possible.
I tried to first select all cameras (ctrl A), then right click mouse, and press 'check'
but this doesn't work.
Is there another way as checking each camera manually can be a lot of work with many photo's...
kind regards,
Jan
6
Bug Reports / cannot run last PhotoScan version 1.0.0.1795 in ubuntu 10.04 LTS
« on: January 07, 2014, 05:07:13 PM »
Hello,
I can run a previous stable Photoscan version (0.9.1.1714) in Linux (ubuntu 10.04 LTS), but not the last stable version (i.e. 1.0.0.1795) on the same OS.
Normally I double click on the photoscan.sh file, and then press the button "run in terminal" to open photoscan (this normally works), but with the latest version, nothing happens.
Anybody knowing a solution?
regards,
Jan
I can run a previous stable Photoscan version (0.9.1.1714) in Linux (ubuntu 10.04 LTS), but not the last stable version (i.e. 1.0.0.1795) on the same OS.
Normally I double click on the photoscan.sh file, and then press the button "run in terminal" to open photoscan (this normally works), but with the latest version, nothing happens.
Anybody knowing a solution?
regards,
Jan
7
General / Re: alignment mistakes
« on: November 13, 2013, 08:16:14 PM »
no GPS log. I do have GCPs, but in my case I think I can use these only after the alignment process because the GCPs are not distinguishable from each other. Once the photos are correctly aligned, I can see the pattern of the GCPs, and from this GCP pattern I can assign the correct coordinates to each GCP.
8
General / alignment mistakes
« on: November 13, 2013, 07:31:42 PM »
Hi all,
I often encounter alignment mistakes by PhotoScan. Often Photoscan aligns subsets of photo's right, but these subsets are at angles with each other (resulting in intersecting planes). I should have enough overlap between the pictures. I mostly use a lot of pictures (2000 and more), but I have a quiet powerful PC (24 GB RAM, i7 hexacore, GeForce GTX 580) so here is no problem. Mostly I align at medium quality, and this will take about 30 to 40 hours or so to align. Do you think that aligning at high quality will reduce this problem? Is there anything else I could do? I'm using aerial photos from a desert, but there are a lot of bushes present, so there are in my opinion enough features to be able to align correctly. In matter of fact, as explained above, PhotoScan does align correctly, but only within subsets. These subsets are however at angles with each other...
I often encounter alignment mistakes by PhotoScan. Often Photoscan aligns subsets of photo's right, but these subsets are at angles with each other (resulting in intersecting planes). I should have enough overlap between the pictures. I mostly use a lot of pictures (2000 and more), but I have a quiet powerful PC (24 GB RAM, i7 hexacore, GeForce GTX 580) so here is no problem. Mostly I align at medium quality, and this will take about 30 to 40 hours or so to align. Do you think that aligning at high quality will reduce this problem? Is there anything else I could do? I'm using aerial photos from a desert, but there are a lot of bushes present, so there are in my opinion enough features to be able to align correctly. In matter of fact, as explained above, PhotoScan does align correctly, but only within subsets. These subsets are however at angles with each other...
9
General / too many overlapping pictures (how to thin them automatically?)
« on: November 11, 2013, 08:39:55 PM »
Hi, I've not been using Photoscan for a while, but I'm going to use it again now.
I've a new collection of photos (about 5000 of them) of a landscape acquired by interval-shooting from a drone. However there is too much overlap-area between the photos. Although this is of course better than too few overlap, aligning 5000 photos will take too much time. Do I have to thin this photo collection manually (which also will take a lot of time with 5000 pictures!), or can this photo thinning be performed automatically in Photoscan.
In case that such function is not (yet?) implemented in Photoscan this may be considered as a feature request... It would be so nice if Photoscan could automatically take a suitable (or even optimal in terms of processing time) subset of photos from a photo-set with too many pictures (i.e. too much overlapping area between all pictures in the set). In this way computing time could be (sometimes highly) reduced by omitting superfluous data.
best wishes,
Jan
I've a new collection of photos (about 5000 of them) of a landscape acquired by interval-shooting from a drone. However there is too much overlap-area between the photos. Although this is of course better than too few overlap, aligning 5000 photos will take too much time. Do I have to thin this photo collection manually (which also will take a lot of time with 5000 pictures!), or can this photo thinning be performed automatically in Photoscan.
In case that such function is not (yet?) implemented in Photoscan this may be considered as a feature request... It would be so nice if Photoscan could automatically take a suitable (or even optimal in terms of processing time) subset of photos from a photo-set with too many pictures (i.e. too much overlapping area between all pictures in the set). In this way computing time could be (sometimes highly) reduced by omitting superfluous data.
best wishes,
Jan
10
General / Re: "Can't build model" when trying to Build Geometry
« on: April 29, 2013, 07:39:09 PM »
Hello Alexey,
I do not have a priori camera position. However after alignment, photoscan seems to reconstruct these camera coordinates correctly.
All camera instances are unchecked in the ground control pane.
The bounding box contains the point cloud and also the by Photoscan calculated camera positions.
Below is the text generated by the console, when trying to build geometry (after this a pop-up appears saying 'Can't build model'):
Using device: GeForce GTX 580, 16 compute units, 1503 MB global memory
max work group size 1024
max work item sizes [1024, 1024, 64]
max mem alloc size 375 MB
max workgroup size c1: 1024 c3: 1024 zero: 1024 hamming: 1024 filter: 1024 box: 1024
max workgroup size zero: 1024 costs: 1024 b1: 1024 bn: 1024 wta: 1024 transpose: 1024
initializing...
selected 0 cameras from 214 in 0.024 sec
Loading photos...
Reconstructing depth...
finished depth reconstruction in 0.015 seconds
Device 1 performance: 0 million samples/sec (CPU)
Device 2 performance: 0 million samples/sec (GeForce GTX 580)
Generating mesh...
Finished processing in 0.54 sec (exit code 0)
I do not have a priori camera position. However after alignment, photoscan seems to reconstruct these camera coordinates correctly.
All camera instances are unchecked in the ground control pane.
The bounding box contains the point cloud and also the by Photoscan calculated camera positions.
Below is the text generated by the console, when trying to build geometry (after this a pop-up appears saying 'Can't build model'):
Using device: GeForce GTX 580, 16 compute units, 1503 MB global memory
max work group size 1024
max work item sizes [1024, 1024, 64]
max mem alloc size 375 MB
max workgroup size c1: 1024 c3: 1024 zero: 1024 hamming: 1024 filter: 1024 box: 1024
max workgroup size zero: 1024 costs: 1024 b1: 1024 bn: 1024 wta: 1024 transpose: 1024
initializing...
selected 0 cameras from 214 in 0.024 sec
Loading photos...
Reconstructing depth...
finished depth reconstruction in 0.015 seconds
Device 1 performance: 0 million samples/sec (CPU)
Device 2 performance: 0 million samples/sec (GeForce GTX 580)
Generating mesh...
Finished processing in 0.54 sec (exit code 0)
11
General / Re: which camera for low-altitude aerial photography (for use with PhotoScan)?
« on: April 23, 2013, 04:14:40 PM »
For those interested, I made good pictures with 1/2000 shutter speed, 400 ISO and infinity focus in high light intensity outdoor areas. The speed of the kopter was 15 km/h (4.2 m/s). I used a Canon IXUS 220hs, with the following CHDK intervalometer script (which I found on http://chdk.setepontos.com/index.php?topic=8984.15), hereby shooting an image every 1.5 seconds.
this CHDK lua intervalometer script is written below
--[[
@title UAV Shooter 4
@param a Delay Start (Min)
@default a 0
@param b Delay Start (Sec)
@default b 20
@param c Number of Shots
@default c 50
@param d Interval (Sec)
@default d 2
@param e Interval (1/10 Sec)
@default e 5
@param g Endless? No=0 Yes=1
@default g 0
@param l LCD off? Yes=0 No=1
@default l 0
--]]
function restore()
release("shoot_half")
set_aflock(0)
set_record(0)
set_backlight(0)
end
interval=d*1000+e*100
wait=a*60000+b*1000
shotcount=0
set_console_layout(1,1,40,13)
print("startup delay - LCD off")
sleep(1000)
set_backlight(l)
sleep(wait)
print("running")
if( get_mode() ==false ) then
set_record(1)
while ( get_mode() == false ) do
sleep(100)
end
end
press("shoot_half")
repeat sleep(100) until get_shooting() == true
set_aflock(1)
print("focus locked")
nextshot=get_tick_count()
starttime=nextshot
repeat
shotcount=shotcount+1
print ( "shot", shotcount, "at", ((get_tick_count()-starttime)/1000),"sec. Err=", (nextshot-get_tick_count()), "mSec" )
nextshot=nextshot+interval
ecnt=get_exp_count()
press("shoot_full_only")
repeat
sleep(20)
until(get_exp_count()~=ecnt)
release("shoot_full_only")
while ( nextshot > get_tick_count()) do
set_backlight(l)
sleep(50)
end
until ( (g==0) and (shotcount >= c))
restore()
this CHDK lua intervalometer script is written below
--[[
@title UAV Shooter 4
@param a Delay Start (Min)
@default a 0
@param b Delay Start (Sec)
@default b 20
@param c Number of Shots
@default c 50
@param d Interval (Sec)
@default d 2
@param e Interval (1/10 Sec)
@default e 5
@param g Endless? No=0 Yes=1
@default g 0
@param l LCD off? Yes=0 No=1
@default l 0
--]]
function restore()
release("shoot_half")
set_aflock(0)
set_record(0)
set_backlight(0)
end
interval=d*1000+e*100
wait=a*60000+b*1000
shotcount=0
set_console_layout(1,1,40,13)
print("startup delay - LCD off")
sleep(1000)
set_backlight(l)
sleep(wait)
print("running")
if( get_mode() ==false ) then
set_record(1)
while ( get_mode() == false ) do
sleep(100)
end
end
press("shoot_half")
repeat sleep(100) until get_shooting() == true
set_aflock(1)
print("focus locked")
nextshot=get_tick_count()
starttime=nextshot
repeat
shotcount=shotcount+1
print ( "shot", shotcount, "at", ((get_tick_count()-starttime)/1000),"sec. Err=", (nextshot-get_tick_count()), "mSec" )
nextshot=nextshot+interval
ecnt=get_exp_count()
press("shoot_full_only")
repeat
sleep(20)
until(get_exp_count()~=ecnt)
release("shoot_full_only")
while ( nextshot > get_tick_count()) do
set_backlight(l)
sleep(50)
end
until ( (g==0) and (shotcount >= c))
restore()
12
General / "Can't build model" when trying to Build Geometry
« on: April 19, 2013, 08:13:01 PM »
Hello,
I want to make a low quality model from 175 pictures, as I want to have it fast to have a preview.
the pictures were aligned well in low quality mode. However when executing the "Build Geometry..." step, PhotoScan immediately comes with a tiny pop-up window that says: "Can't build model".
The camera positions are displayed above the point cloud, and they seem to be correct. However in the cameras panel, all camera coordinates are all 0.
I'm using PhotoScan 0.9.0 build 1586
What could be wrong?
I want to make a low quality model from 175 pictures, as I want to have it fast to have a preview.
the pictures were aligned well in low quality mode. However when executing the "Build Geometry..." step, PhotoScan immediately comes with a tiny pop-up window that says: "Can't build model".
The camera positions are displayed above the point cloud, and they seem to be correct. However in the cameras panel, all camera coordinates are all 0.
I'm using PhotoScan 0.9.0 build 1586
What could be wrong?
13
General / Re: which camera for low-altitude aerial photography (for use with PhotoScan)?
« on: April 16, 2013, 08:40:02 PM »
Thanks RalfH, I made similar calculations, and I came to a similar conclusion (i.e. starting with 1ms). Didn't thought about other camera movements though. In the next days I will trial and error...
14
General / Re: which camera for low-altitude aerial photography (for use with PhotoScan)?
« on: April 14, 2013, 10:28:51 AM »
We've finally bought a Canon Ixus 220hs, and it seems to work fine, at least on the ground. With a CHDK script I've managed to set the frequency of the intervalometer to a bit less than 1 picture a second. Other camera properties are also nice (only 140 gram, only 140 euros, 24 mm focal length)
I'm now wondering what shutter speed, ISO value combination I should use. Of course I will trial and error on the field, but maybe somebody knows a good initial parameter combination to start from?
I will use the UAV at 20 m height, and it will fly 15 km/h. Does somebody has experience with estimating good shutter speed and ISO value combinations with UAV photography? I will take pictures in very sunny areas (in the desert).
I'm now wondering what shutter speed, ISO value combination I should use. Of course I will trial and error on the field, but maybe somebody knows a good initial parameter combination to start from?
I will use the UAV at 20 m height, and it will fly 15 km/h. Does somebody has experience with estimating good shutter speed and ISO value combinations with UAV photography? I will take pictures in very sunny areas (in the desert).
15
General / Re: which camera for low-altitude aerial photography (for use with PhotoScan)?
« on: April 09, 2013, 01:58:51 PM »
Thanks RalfH, good to know this,
Jan
Jan
