TOF-SANS Working Group - Revision history

Annikastellhorn at 08:50, 5 November 2024

2024-11-05T08:50:32Z

← Older revision	Revision as of 08:50, 5 November 2024
Line 35:	Line 35:


		= Session Notes SAS2024 - Sun 2024-11-03 =

		=== To-Dos! ===
		* How to store the resolution information?
		* How to treat nD data (1D,2D,3D)?
		* How do we know which resolution function is the right one? Note: We need a reference sample to verify which one is the right resolution function!
		* Visualization?
		* How can the information be implemented into nxcansas?
		* How can the information be implemented into relevant analysis software (e.g. sasview)?
		* How to take into account inelastic effects? Can this be addressed be the correct choice of standard samples? Who knows about standard samples including such effects?
		* How do we take into account multiple scattering?

		=== Notes from the discussion round: ===
		* The topic about resolution functions for different instruments/techniques needs an extra working group!
		* For the other notes on resolution functions, please be referred to the notes of the SAS2024 working group discussion of Data formats.

Smk at 14:15, 16 April 2024

2024-04-16T14:15:24Z

← Older revision		Revision as of 14:15, 16 April 2024
Line 5:		Line 5:
	* Judith Houston (ESS)		* Judith Houston (ESS)
	* Adrian Rennie (Uppsala)		* Adrian Rennie (Uppsala)
	* Wojciech Potrzebowski (~~ESS~~)		* Wojciech Potrzebowski (SciLifeLab)

	===News/Status===		===News/Status===

Wpotrzebowski at 20:52, 20 March 2024

2024-03-20T20:52:38Z

← Older revision		Revision as of 20:52, 20 March 2024
Line 28:		Line 28:
	Few other open issues not covered with the information above:		Few other open issues not covered with the information above:

	~~In an ideal world the spacings~~ of resolution curve could match the Q spacings of the I(Q) ~~data to save an interpolation step by directly giving the coefficients of the other calculated I(Q~~) ~~points. But again this should be avoided due to messy issues close to the beam stop, and problems if users crop or rebin data.~~		* Spacings of resolution curve still needs to be defined (in principle it could match the Q spacings of the I(Q))

	~~The potential solution would be~~ to ~~perform resolution convolution so~~ the model fit Icalc(Q) is interpolated to match the Q values. Ideally, the fitting code would recalculate I(Q) at precise points, or at least on a finer grid, if sharp features are either found or expected.		* Think about whether to use anything more advanced that Trapezium Rule for the integrations.

	~~CHECK: This is the opposite of what Sasview does at present, which is to calculate the value of the Gaussian resolution for a given Q at the adjacent Q values already available for I(Q).~~		* Think about Q resolution for 2d data!

	~~Also need to think about whether to use anything more advanced that Trapezium Rule for the integrations.~~

	~~TODO: think~~ about Q resolution for 2d data!

Wpotrzebowski at 11:53, 20 March 2024

2024-03-20T11:53:38Z

← Older revision		Revision as of 11:53, 20 March 2024
Line 27:		Line 27:

	Few other open issues not covered with the information above:		Few other open issues not covered with the information above:

	In an ideal world the spacings of resolution curve could match the Q spacings of the I(Q) data to save an interpolation step by directly giving the coefficients of the other calculated I(Q) points. But again this should be avoided due to messy issues close to the beam stop, and problems if users crop or rebin data.		In an ideal world the spacings of resolution curve could match the Q spacings of the I(Q) data to save an interpolation step by directly giving the coefficients of the other calculated I(Q) points. But again this should be avoided due to messy issues close to the beam stop, and problems if users crop or rebin data.

Wpotrzebowski at 11:52, 20 March 2024

2024-03-20T11:52:00Z

← Older revision		Revision as of 11:52, 20 March 2024
Line 22:		Line 22:
	* '''Loading.''' NXCanSAS files with resolution functions need to be loaded by the analysis software. It will require development in SasView.		* '''Loading.''' NXCanSAS files with resolution functions need to be loaded by the analysis software. It will require development in SasView.
	* '''Visualization.''' Majority of users will probably apply resolution as it is. It may however be useful to be able to plot individual resolution curves and for example, compare it with Gaussian estimates. There may also be some option for changing sampling. This part needs to be defined and developed.		* '''Visualization.''' Majority of users will probably apply resolution as it is. It may however be useful to be able to plot individual resolution curves and for example, compare it with Gaussian estimates. There may also be some option for changing sampling. This part needs to be defined and developed.
	* '''Computation.''' Proof-of-concept of applying full resolution curve has been demonstrated using SasView: https://github.com/SasView/sasview/blob/generic_resolution/notebooks/GenericResolutionPOC.ipynb		* '''Computation.''' Proof-of-concept of applying full resolution curve has been demonstrated using SasView: https://github.com/SasView/sasview/blob/generic_resolution/notebooks/GenericResolutionPOC.ipynb. (Also https://github.com/SasView/sasview/issues/1497)
	* '''Saving.''' The information about the full resolution curve should be carried on as metadata or the report. It needs to be established		* '''Saving.''' The information about the full resolution curve should be carried on as metadata or the report. It needs to be established
	* '''Databases.''' It would also be useful if community supported databases can consume this information (both dQ and full description).		* '''Databases.''' It would also be useful if community supported databases can consume this information (both dQ and full description).

			Few other open issues not covered with the information above:
			In an ideal world the spacings of resolution curve could match the Q spacings of the I(Q) data to save an interpolation step by directly giving the coefficients of the other calculated I(Q) points. But again this should be avoided due to messy issues close to the beam stop, and problems if users crop or rebin data.

			The potential solution would be to perform resolution convolution so the model fit Icalc(Q) is interpolated to match the Q values. Ideally, the fitting code would recalculate I(Q) at precise points, or at least on a finer grid, if sharp features are either found or expected.

			CHECK: This is the opposite of what Sasview does at present, which is to calculate the value of the Gaussian resolution for a given Q at the adjacent Q values already available for I(Q).

			Also need to think about whether to use anything more advanced that Trapezium Rule for the integrations.

			TODO: think about Q resolution for 2d data!

Wpotrzebowski at 11:41, 20 March 2024

2024-03-20T11:41:47Z

← Older revision		Revision as of 11:41, 20 March 2024
Line 12:		Line 12:

	===Generic resolution function===		===Generic resolution function===
	A workflow for utilizing the full resolution curve is ~~depicted~~ in ~~the~~ figure ~~bellow~~.		A workflow for utilizing the full resolution curve is shown in figure 1.
	[[File:TOF SANS.drawio.png\|thumb\|Generic resolution workflow]]		[[File:TOF SANS.drawio.png\|thumb\|Fig. 1. Generic resolution workflow]]

	In order to avoid repetitions and keep the message coherent, bellow I provided mostly the collection of relevant links and current status (March 2024).		In order to avoid repetitions and keep the message coherent, bellow I provided mostly the collection of relevant links and current status (March 2024).

Wpotrzebowski at 11:39, 20 March 2024

2024-03-20T11:39:54Z

← Older revision		Revision as of 11:39, 20 March 2024
Line 2:		Line 2:
	* Andrew Jackson (ESS)		* Andrew Jackson (ESS)
	* Anna Sokolova (ANSTO)		* Anna Sokolova (ANSTO)
	* Sebastian Jaksch (~~JCNS~~)		* Sebastian Jaksch (ESS)
	* Judith Houston (ESS)		* Judith Houston (ESS)
	* Adrian Rennie (Uppsala)		* Adrian Rennie (Uppsala)
Line 12:		Line 12:

	===Generic resolution function===		===Generic resolution function===
	* ~~Description about~~ how to ~~handle generic~~ resolution ~~function~~ in ~~SANS~~		A workflow for utilizing the full resolution curve is depicted in the figure bellow.
			[[File:TOF SANS.drawio.png\|thumb\|Generic resolution workflow]]

			In order to avoid repetitions and keep the message coherent, bellow I provided mostly the collection of relevant links and current status (March 2024).

			* '''Input''' data consists of instrumental parameters and shapes of corresponding terms contributing to the resolution function. Please check https://github.com/scipp/esssans/issues/111 for more details
			* '''Convolution.''' Following developments in GRASP individual resolution kernels are convoluted rather than collapsed to a single number (as classically has been done with Milldner-Carpenter equation). Please review Jupyter notebook on how this can be potentially done https://github.com/scipp/esssans/files/14509637/checkbox-convolution.ipynb.zip
			* '''Resolution curve. '''The full-resolution curves (defined per q points) are saved to NXCanSAS file. Anticipates entries are /entry/data/q/resolutions and /entry/data/q/resolutions_descriptions. dQ as a single number should always be provided.
			* '''Loading.''' NXCanSAS files with resolution functions need to be loaded by the analysis software. It will require development in SasView.
			* '''Visualization.''' Majority of users will probably apply resolution as it is. It may however be useful to be able to plot individual resolution curves and for example, compare it with Gaussian estimates. There may also be some option for changing sampling. This part needs to be defined and developed.
			* '''Computation.''' Proof-of-concept of applying full resolution curve has been demonstrated using SasView: https://github.com/SasView/sasview/blob/generic_resolution/notebooks/GenericResolutionPOC.ipynb
			* '''Saving.''' The information about the full resolution curve should be carried on as metadata or the report. It needs to be established
			* '''Databases.''' It would also be useful if community supported databases can consume this information (both dQ and full description).

Wpotrzebowski at 14:01, 19 March 2024

2024-03-19T14:01:25Z

← Older revision		Revision as of 14:01, 19 March 2024
Line 11:		Line 11:
	* The workshop about TOF resolution was held in March 2021 (online): https://indico.esss.lu.se/event/2506/		* The workshop about TOF resolution was held in March 2021 (online): https://indico.esss.lu.se/event/2506/

			===Generic resolution function===
			* Description about how to handle generic resolution function in SANS

Wpotrzebowski at 13:03, 9 March 2022

2022-03-09T13:03:59Z

← Older revision		Revision as of 13:03, 9 March 2022
Line 9:		Line 9:
	===News/Status===		===News/Status===
	* Working group formed at canSAS-XI in Freising		* Working group formed at canSAS-XI in Freising
			* The workshop about TOF resolution was held in March 2021 (online): https://indico.esss.lu.se/event/2506/

Wpotrzebowski: /* Members */

2022-03-09T13:01:44Z

Members

← Older revision		Revision as of 13:01, 9 March 2022
Line 5:		Line 5:
	* Judith Houston (ESS)		* Judith Houston (ESS)
	* Adrian Rennie (Uppsala)		* Adrian Rennie (Uppsala)
			* Wojciech Potrzebowski (ESS)

	===News/Status===		===News/Status===