Messages

13066

Face and Body Scanning / Re: Help ! can't create complete mesh.

« on: May 14, 2014, 07:17:55 AM »

Hello agga,

If possible, please send the link to the dataset to support@agisoft.ru.

One of the most probable reasons of the problem is insufficient number of matching points found on the face/head. It may be caused by ineffective use of frame space, for example, the face occupies only a small area on the image, or the image is too noisy or is not focused properly on the object.

13067

Python and Java API / Re: Python scripts fails on launch but works in console?

« on: May 14, 2014, 07:09:01 AM »

Hello nickponline,

Access to PhotoScan.app.document is blocked for scripts put in autostart folder. So to start processing script it is necessary to run it from GUI via Run Script dialog or custom menu item created using autorun scripts.

13068

General / Re: stability problems release 1.0.4 build 1847

« on: May 13, 2014, 09:01:18 PM »

Unless we are mistaken, we've found the crash report and it seems that crashes are caused by the graphic card drivers, so we recommend to use latest drivers available for the graphic card.

13069

General / Re: stability problems release 1.0.4 build 1847

« on: May 13, 2014, 05:51:55 PM »

Hello Frank,

Unfortunately, we can't find the crash report from you. In case you can reproduce the crash and submit the report once again, we'll appreciate it.

13070

General / Re: orientation of the z-axis

« on: May 13, 2014, 05:26:57 PM »

Hello anabento,

If you are speaking of referenced models with the input coordinates of cameras and/or markers. Than the most likely reason is incorrect import of the coordinate information - X and Y columns are mixed, causing inverted Z-axis.

13071

General / Re: stability problems release 1.0.4 build 1847

« on: May 13, 2014, 05:24:57 PM »

Hello Frank,

Have you submitted the crash reports using crash reporter tool? If not, could you please do so and sign the report, so that we can easily identify it and check the problem.

Also please check RAM modules using Memtest86 utility, just for case.

13072

Python and Java API / Re: more on Import and Export Cameras python commands

« on: May 12, 2014, 04:19:12 PM »

Hello lmg,

So you need to generate text file using etimated camera locations to be loaded in the new projects/chunks using ground_control.load option? I'll post export code a little bit later, but using Ground Control pre-selection is not reasonable in four camera case., unless you need to reference the chunk using previously obtained coordinates.

13073

Bug Reports / Re: Masks

« on: May 11, 2014, 05:12:55 PM »

Hello Miles,

Could you lease post the screenshot of Import Masks dialog with the parameters you are using and also specify the naming convention for original images and mask files.

13074

General / Re: Volume/Area Calculation and QA/QC

« on: May 10, 2014, 08:57:23 PM »

Hello aggieair,

PhotoScan calculates area of the surface as a sum of areas for all the faces in the model, so if you've closed volume prior to calculation bottom area will be also calculated. Also note that side polygons will be also taken into account, so the result will be greater than area of 2D projection of the model to the XY plane.

You can use Generate report feature after cutting the unwanted faces to get area of 2D projection.

13075

Python and Java API / Re: matchPhotos() not using all CPU cores?

« on: May 07, 2014, 12:30:22 PM »

Hello WickedShell,

Detecting points stage really works with single photo at a time and currently we are not planning to change it, to avoid much higher memory consumption related to the simultaneous feature point detection on multiple images. Usually time required for point detection stage is much lower than time required for photo matching, so at the moment we are not planning to change the things, at least not for the next version.

And such behavior is related not only with Python command and is actually the same for common processing workflow via GUI.

13076

Bug Reports / Re: Image paths problem

« on: May 06, 2014, 02:47:55 PM »

Hello Heinrich,

By default PhotoScan saves relative paths to the image files.

To fix the problem with wrong paths after moving the file folder relative to the project file, it is recommended to use Change Path option from the Photos pane context menu.

13077

Other Languages / Re: Несколько проблем

« on: May 06, 2014, 02:12:20 PM »

Спасибо за предоставленные данные.

Воспроизвести проблему с неправильным отображением значений с плавающей точкой пока не удаётся - в обоих проектах значения адекватные, так что пока ещё неясно, почему в Вашем случае отображается только первая ненулевая значащая цифра.

Что касается самих фотографий, то можно было бы направить камеру чуть вбок, чтобы не захватывать положение съёмки следующего кадра.
Однако, в следующей версии мы планируем улучшить обработку кадров, сделанных подобным образом. Ниже результат обработки Вашего проекта с использованием улучшений из следующей версии:

13078

Python and Java API / Re: Python Scripting

« on: May 06, 2014, 12:29:22 PM »

Dear studentTUBAF,

The script adds new option in Custom Menu (in Main Menu), so to run the processing you need to choose this newly created option.

Maybe you can provide a sample dataset for 4D processing?

13079

Other Languages / Re: Несколько проблем

« on: May 06, 2014, 12:11:15 PM »

Добрый день,

Не могли бы Вы прислать проект, желательно с исходными кадрами?


Что касается невозможности построения плотного облака, то это может быть связано не только с проблемами калибровки (значения Fx, Fy, Cx, Cy выглядят явно странными), но и с тем, что съёмка велась таким образом, что камеры "видят" положения практически всех остальных камер. Такие пары отфильтровываются на этапе построения карт глубины. Обычно это характерно для случаев, когда камера двигалась в  направлении своей зоны видимости.

Пожалуйста, сообщите ещё версию ОС.

13080

Python and Java API / Re: Equivalent of Tools > Import > Import Markers in python scripting?

« on: May 06, 2014, 10:53:55 AM »

For example, if you have list of coordinates represented as tuples I can suggest the following code, providing that markers have been already created:

Code: [Select]

doc  = PhotoScan.app.document
chunk = activeChunk

coordinate_list = [(93.33312, 24.565464, 178.5), (93.4657, 24.7345, 175.23)]
#list of tuples with the coordinates to be imported

markers = chunk.markers
locations = chunk.ground_control.locations

for i in range(len(markers)):
    marker = markers[i]
    marker_coords = locations[marker]
    marker_coords  = coordinate_list[i]
   
chunk.ground_control.apply()
PhotoScan.app.update()