Opened 6 years ago

Closed 5 years ago

#467 closed bug (fixed)

Reading in time0 fields

Reported by: srkline Owned by: srkline
Priority: major Milestone: VSANS File Definition
Component: All Components Keywords:
Cc: Blocking:


get rid of the nx_distane fields from the JS file and from any Igor definition that I have lying around.

I may be stuck with the nx_time fields - I'm not sure what happens to these when they are read in --??

Change History (5)

comment:1 Changed 6 years ago by srkline

  • Summary changed from nx_distance fields to Reading in time0 fields

distance was my own function, and I've renamed that to avoid the conflict. time is still an Igor keyword. "time" is then read in and automatically renamed to "time0". I simply need to plan for this when reading in time fields

all of the nx_ named fields have been removed from JS and OO files.

comment:2 Changed 6 years ago by srkline

note that this pertains ONLY to the READ of these fields from the LOCAL copy of the value. The field in the Nexus file will always be named "time".

Also be sure to use the correct name for WRITE, since the file is expecting "time"

comment:3 Changed 6 years ago by srkline

needs to be verified, but the code appears to be correct

comment:4 Changed 6 years ago by srkline

It looks like the only issue will be with the "time" field of the temperature sensor. Either expect it to be "mis-read" as "time0" and force my own name when I read the local array to plot it - or maybe come up with a different name to start with in the data file that is unique. clashing with a very common O/S keyword is rather lousy for Nexus behavior.

comment:5 Changed 5 years ago by srkline

  • Resolution set to fixed
  • Status changed from new to closed

if I hard-wire the read as time0, and the write as time, then I should be fine. done in r1005, will test when I get real sensor data arrays to work with.

Note: See TracTickets for help on using tickets.