Context Navigation

Ticket #11184 (closed: fixed)

Opened 6 years ago

Last modified 5 years ago

Allow plus created event file to be processed with ISIS SANS

Reported by:	Anders Markvardsen	Owned by:	Peter Parker
Priority:	critical	Milestone:	Release 3.4
Component:	SANS	Keywords:
Cc:	peter.parker@…, sarah.rogers@…, anton.piccardo-selg@…	Blocked By:	#11351
Blocking:		Tester:	Martyn Gigg

Description (last modified by Anders Markvardsen) (diff)

Take e.g. the SANS2D event runs 26995 and 27019 and add these together, but not adding these into a histogram workspace file. Instead into an event workspace file that can then subsequently be processed with the ISIS SANS interface in the same way as a standard event nexus file.

Attachments

USER_SANS2D_143AB_5_12m_Xpress_M3_8mm.txt (2.3 KB) - added by Anton Piccardo-Selg 5 years ago.
DIRECT_SANS2d_27511_12m_Rear_23Mar15.txt (8.0 KB) - added by Anton Piccardo-Selg 5 years ago.

Change History

comment:1 Changed 6 years ago by Anders Markvardsen

Status changed from new to assigned

comment:2 Changed 6 years ago by Anders Markvardsen

Description modified (diff)

From meeting earlier this week. Hard deadline is end of April for this feature.

Steps to implement this.

Run e.g. SANS2D 26995 insuring that monitors are loaded

Put the two created workspaces into a group, monitors and event data and save this group as a processed mantid nexus workspace

Monitor the sans code so that when doing the initial loading the workspaces you get from loading 2) exactly same loading from 1). Then the remaining code can stay the same.

comment:3 Changed 6 years ago by Anders Markvardsen

Blocking 11351 added

comment:4 Changed 6 years ago by Anders Markvardsen

Owner changed from Anders Markvardsen to Peter Parker

comment:5 Changed 6 years ago by Peter Parker

Cc anton.piccardo-selg@… added
Status changed from assigned to verify
Resolution set to invalid

Sarah:

After some further investigation / discussion surrounding this ticket, we've come to the conclusion that this functionality is actually already available in Mantid, albeit not using the "Add Runs" tab of the ISIS SANS interface:

Load the Event files you want to add (using the Load algorithm and not the "Load Data" button of the interface).
Use the Plus algorithm to add the event workspaces together. Obviously if you have more than 2 files it's going to require multiple calls to Plus.
Save the result to file by right-clicking the workspace and pressing "Save Nexus". Make sure to name the file as per the "Add Runs" tab's naming convention (i.e. "SANS2DNNNNNNN-add.nxs").

We've tried this with 26995 and 27019 and the resulting file goes through the reducer well enough.

In the meantime, we have #11351 to allow this to work as part of the "Add Runs" tab. Anton and I will be looking into this tomorrow. We will get back to you when we've implemented it.

comment:6 Changed 6 years ago by Anders Markvardsen

Status changed from verify to verifying
Tester set to Anders Markvardsen

comment:7 Changed 6 years ago by Anders Markvardsen

Status changed from verifying to reopened
Resolution invalid deleted

Doing the following:

I used user file: C:/Backup/Backup_folder1/work/code/Mantid/git/mantid2/Test/systemtests/Data/SANS2D/MASKSANS2D.091A

Load
isis\inst$\NDXSANS2D\Instrument\data\cycle_14_2\SANS2D00026995.nxs without the Load diaglog LoadMonitors tick-box ticked generates one event workspace SANS2D00026995. However right clicking and selecting 'Show detectors', there are no monitor data

Repeating the above I with LoadMonitors tick-box ticked at I get two workspaces

Jointly with Anton I can't reproduce the above results. I.e. loading using steps in 1 for both 26995 and 27019, etc, and my Mantid version is not happy.

I spoke to Sarah and she says, to her knowledge the monitor data are stored as histogram data.

If the LoadMonitors is not ticked I struggle to see how the save nexus file can contain monitor data. If this is the case it is a bug

Peter/Anton please try this a second time