Opened 9 years ago
Closed 9 years ago
#373 closed defect (fixed)
2D data loader issue
| Reported by: | butler | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | SasView 3.1.0 |
| Component: | SasView | Keywords: | data loader, 2D data |
| Cc: | Work Package: | SasView Bug Fixing |
Description
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)?
Change History (2)
comment:1 Changed 9 years ago by krzywon
comment:2 Changed 9 years ago by krzywon
- Resolution set to fixed
- Status changed from new to closed
I downloaded the newest build (#125) and 1D and 2D data is now loading as expected.
Note: See
TracTickets for help on using
tickets.
I tried loading various file types and found that none of the meta data was getting loaded in unless the data file type was cansas xml. If no known readers are available, SasViews? defaults to the cansas loader (1st) and if that fails, the ascii reader is used which ignores all header data.
I looked and noticed the defaults.json file defining the data loaders wasn't being bundled with the windows build. The setup_exe.py file was was still trying to load in the old defaults.xml file, so I changed that and pushed, and hopefully the next build will fix this issue. The setup_mac.py file was loading the correct defaults file.