Finding out ORGX ORGY: Difference between revisions

Finding out ORGX ORGY (view source)

Revision as of 16:17, 2 June 2014

130 bytes added , 2 June 2014

no edit summary

Kay

Bureaucrats

2,652

edits

Revision as of 20:00, 27 February 2012 (view source) Kay (talk \| contribs) (→‎The case of a swung-out detector) ← Older edit		Revision as of 16:17, 2 June 2014 (view source) Kay (talk \| contribs) No edit summary Newer edit →
Line 9:		Line 9:
	# use the Unix command line tools to look at the header of the frame. E.g. "strings <frame-name>\|more" would should you the (hopefully correct) information stored in the header, like wavelength, delta-phi, X and Y beamcentre and so on.		# use the Unix command line tools to look at the header of the frame. E.g. "strings <frame-name>\|more" would should you the (hopefully correct) information stored in the header, like wavelength, delta-phi, X and Y beamcentre and so on.

	The error you make in the determination of ORGX ORGY should in principle be less than half of the distance between two spots. If you have a reasonable estimate (from one of the methods above), but the error is bigger than that, ''you can still find out the true ORGY ORGY by inspecting [[IDXREF.LP]] . This works best if [[COLSPOT]] has seen a significant fraction of all frames.''		The error you make in the determination of ORGX ORGY should in principle be less than half of the distance between two spots. If you have a reasonable estimate (from one of the methods above), but the error is bigger than that, ''you can still find out the true ORGY ORGY by inspecting [[IDXREF.LP]] . This works best if [[COLSPOT]] has seen a significant fraction of all frames.'' This procedure is [[Thaumatin_ACA2014#Digression:_a_computational_investigation_into_the_robustness_of_the_indexing\|documented]].