Ticket #4209 (closed: fixed)
Additional lines in GSAS file
Reported by: | Peter Peterson | Owned by: | Peter Peterson |
---|---|---|---|
Priority: | minor | Milestone: | Release 2.0 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Shelly Ren |
Description
In order to play nicer with GSAS and PDFgetN the gsas files should get a couple of additional lines. An example from PDFgetN tutorial data
Background Measurement (Displex Heatshield) Instrument parameter file: calib/npdf_displex_184.iparm Monitor: 1 #------------------------------------------------------------------------------- # Filename : archive/NPDF_E000002_R000231.nx.hdf # Experiment_number : 2 # Run_number : 231
It is only lines 2 and 3 that need to be added.
Change History
comment:2 Changed 9 years ago by Peter Peterson
Adding monitor counts for gsas. Refs #4209.
Changeset: 4ff126d30830b725b082657a934b4df4a41f52c9
comment:3 Changed 9 years ago by Peter Peterson
Adding the magic two lines. Refs #4209.
Changeset: 1f16b1cb77c3068adfeb09a4be8dfaf4ea4e1483
comment:4 Changed 9 years ago by Russell Taylor
Revert "Adding the magic two lines. Refs #4209." to fix builds.
This reverts commit 1f16b1cb77c3068adfeb09a4be8dfaf4ea4e1483.
Changeset: 06ba24e29abdff94250e2eb03afe87b39ee6f0e4
comment:5 Changed 9 years ago by Peter Peterson
Adding more header to GSAS files. Refs #4209.
In order to make the tests happy this is turned off by default and enabled using the 'ExtendedHeader' option.
Changeset: f1f45fcecbc1f8ccd22ab47f1141c5815c554b35
comment:7 Changed 9 years ago by Peter Peterson
- Status changed from accepted to verify
- Resolution set to fixed
The last commit fixed this.
comment:8 Changed 9 years ago by Peter Peterson
- Status changed from verify to reopened
- Resolution fixed deleted
Turns out that if the iparm file is blank gsas gets really grumpy. Remove the line instead.
comment:10 Changed 9 years ago by Peter Peterson
Making the instrument parameter file line better. Refs #4209.
GSAS gets all grumpy if you add a line with a parameter that isn't defined.
Changeset: 6a0b416d6bc0e7c62ae520ce68f982b965de25ab
comment:11 Changed 9 years ago by Peter Peterson
- Status changed from accepted to verify
- Resolution set to fixed
The last commit fixed this.
comment:12 Changed 9 years ago by Peter Peterson
Making the instrument parameter file line better. Refs #4209.
GSAS gets all grumpy if you add a line with a parameter that isn't defined.
Changeset: 6a0b416d6bc0e7c62ae520ce68f982b965de25ab
comment:13 Changed 9 years ago by Shelly Ren
- Status changed from verify to verifying
- Tester set to Shelly Ren
comment:14 Changed 9 years ago by Shelly Ren
- Status changed from verifying to closed
Worked after Refs #6677 is fixed.
Executed SNSPowderReduction python script with the following parameters: instrument: PG3 run number: 2538 CalibrationFile: /SNS/PG3/2011_2_11A_CAL/PG3_FERNS_d4832_2011_08_24.cal CharacterizationRunsFile /home/3qr/PG3_11_22_11.txt Binning: 0.1,-0.0004,10 where /home/3qr/PG3_11_22_11.txt is like Instrument parameter file: PGS_11_22_11.prm 1 2 15 2 2 31 3 2 67 4 2 122 5 2 154 6 2 7 L1 19.5
The 2nd and 3rd line of the output gsa file contained: Instrument parameter file: PGS_11_22_11.prm Monitor: 1
comment:15 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 5056
Getting the iparm filename into the workspace. Refs #4209 and #2320.