EMsoft-org / EMSphInx

C++ Spherical Indexing repository
GNU General Public License v2.0
8 stars 20 forks source link

Opening .ang files created by EMSphInx in OIM software #3

Open smurray94 opened 4 years ago

smurray94 commented 4 years ago

Hey Will,

I am interested in opening up the .ang files produced by EMSphInx within the OIM software package. I prefer to use these packages for clean-up and processing. In particular, I am using OIM v8.1.0. When I try to open the .ang produced by SphInx, only the top row of data will appear when I attempt to create IPF or CI maps. I can see that the .ang file does indeed contain all of the data from SphInx, so something is not translating correctly when opening in OIM.

TSL_output.txt Sphinx_output.txt

RoomTemp_EBM_APrinted_HoughIPF RoomTemp_EBM_AsPrinted_SphinxIPF Opening_SphInxAngFile_inOIM

Many thanks, Sean Murray

smurray94 commented 4 years ago

P.S. Above, I have attached two text files which contain the headers and the first few rows of data for .ang files made from both TSL and from SphInx.

As ever, Sean Murray

wlenthe commented 4 years ago

EMSphInx writes out angs using an older standard (different header format), but it should be readable with OIM analysis. It looks like you're using an older commit (since the pattern center is undefined) and I've updated a few things for better conformance when writing angs so the latest commit may work. I'll try to get a new release out with binaries by the end of the week, but In the mean time you'll have to build your own binaries. If you could upload or email me a full copy of both angs it will be easier to debug, thanks!

smurray94 commented 4 years ago

Update:

The latest version of EMSphInx (0.2) is now working with OIM Analysis v7 on the TriBeam computer at UCSB. However, I still can not seem to open the .ang files on v8 of OIM analysis.

Additionally, I have found that attempting to clean-up data in OIM Analysis v7, the program will crash. I have found that if I clean-up in place, this problem goes away. Additionally, due to the high frequency of crashing, I have found it was easiest to create a .osc, and then proceed from there. .osc files seem to load faster into OIM than .ang files.

As ever, Sean Murray