Through the Interface: Some miscellaneous BrowsePhotosynth changes

Kean Walmsley

May 2015

Sun Mon Tue Wed Thu Fri Sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30


« Some impressive technology | Main | SortOnVersion & ScriptPro »

October 08, 2010

Some miscellaneous BrowsePhotosynth changes

I just thought I’d report back on a few changes made to the BrowsePhotosynth Plugin of the Month during the course of this week. The updated version has just been announced on Scott Sheppard’s blog and I thought I’d share some of the specific implementation details.

The first one (in the 1.0.1 update) was a really interesting problem and I owe a big thanks both to Alberto Venturini for reporting it and to Marat Mirgaleev, from our DevTech team in Moscow, for helping test on a comparable OS. The problem was that on all the systems upon which Alberto had tested, the various points in a Photosynth point cloud would end up on a single axis, essentially at varying distances along a line. We narrowed it down to being locale-related, and then (which I was sleeping on Monday night) the penny dropped and I realised it had to be due to the widespread use of comma as the decimal separator in non-English locales.

The application takes a number of files stored on the Photosynth servers and downloads/processes them, combining the resultant points into a single text file which then gets processed in a LAS file, which they gets indexed as a PCG and attached into AutoCAD. Phew. Here’s that in graphical form (click to enlarge):

BrowsePhotosynth flow chart

The issue was between the F# processor and the txt2las tool: we were clearly writing decimals with comma as the decimal separator to the comma-delimited points.txt file (while txt2las expects period-/full stop-delimited decimals in a comma-delimited file, irrespective of the current locale).

The fix was actually straightforward and applies as well to VB.NET and C# as it does to F#. Here’s an example of an incorrect call:


and here’s what we needed to do, instead, to make sure decimals use a period/full-stop as the decimal point, irrespective of the current locale settings:


We also needed to add the System.Globalization namespace, but that’s about it. Oh, and as we are in F# – which is type-inferred – we had to pin down the values being passed into the function to be of type float32, as the generic object-level ToString() doesn’t have a version taking an IFormatProvider (which CultureInfo.InvariantCulture happens to be).

The next two changes were in the 1.0.2 update that has just been posted: the F# processor’s IsComplete property previously checked the number of files that had been processed. There was an additional callback – AllCompleted – which took care of adding the number of points from each file into a total. So if the loop checked for IsComplete broke and the code went on to check the number of points downloaded – before the AllCompleted event fired – then we would incorrectly report that 0 points had been downloaded and finish the command right there. The fix was to add a boolean flag in the code to be exposed via IsComplete which only gets set to true at the end of AllCompleted.

The second of the 1.0.2 changes was simply to bring down the primary point cloud and none of the additional ones. This is the original implementation I had created, but ended up extending it to pull down multiple point clouds for each Photosynth. The trouble is, the point clouds are kept separate for a good reason: they are not spatially connected (well they actually might be, but that’s a different story and not for today’s post :-) and so have different coordinate systems. I was blindly downloading them and plonking them down into the same coordinate space, which – even if we had more points – led to messier results.

Other Photosynth exporters do provide more information on the various sizes of the point clouds available for each synth, but I’ve opted for simplicity and so just take the first one (which is usually the largest). The code could easily be extended to provide more choice for the user in this area, should anyone feel the need to do so.

Which actually means the results of importing the Menzi Muck synth from the last post (and also it’s new big brother) look better than I’d previously reported.

Hopefully that’s it for the code changes to this tool, for now, but please do let us know if you experience any further issues with it.

blog comments powered by Disqus


10 Random Posts