Both supported 2D data formats fail to read when using the windows installer version. It appears that it is being loaded by the default general ASCII reader (which it goes to if it cannot recognize the file as anything else). It seems to get read correctly on windows development systems however(Jeff K. and Paul B.)

Need to work out why the master build is not building correctly (or why it is different from how it works on development machines)?

User Yuyin Xi reports issue with attached 2d data file.

it is 2d data (from NG7), but not in any of the formats that I could find in our test folder, so over to the NIST guys to work out whether this is an omission or perhaps not fully reduced data? Sasview “successfully” reads it as 1d data, but then throws an error on sending it to fit.

Since the last few days of Code Camp I have been unable to locally build !Sasview using setup.py

I am compiling with disable_openmp build -cmingw32 on W7

Eclipse console returns:

running disable_openmp running build running build_py package init file 'src\sas\sascalc\dataloader\readers\schema\init.py' not found (or not a regular file) running build_ext Compiling with mingw32 (64bit=False)

and then terminates.

Putting in a trap show the problem occurs when the build branches into

build_ext.build_extensions(self)