Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New (?) "Resolution I/sig(I)=2" item in "Auto Processing" table? #700

Open
CV-GPhL opened this issue Dec 3, 2023 · 2 comments
Open

New (?) "Resolution I/sig(I)=2" item in "Auto Processing" table? #700

CV-GPhL opened this issue Dec 3, 2023 · 2 comments

Comments

@CV-GPhL
Copy link

CV-GPhL commented Dec 3, 2023

Just discovered a new column headed "Resolution I/sig(I)=2" at the DLS SynchWeb interface. I guess this means the "resolution where the <I/sigI> of merged reflections (in isotropic shells) drops below 2 when analysed with increasing resolution"? It seems to be populated only by "xia dials" pipelines

Can you please clarify what it exactly means and how other pipeline developers should ensure the value is transferred into ISPyB?

Is this done via the XML file?

@ndg63276
Copy link
Collaborator

ndg63276 commented Dec 4, 2023

Yes I believe that is the case, this was a request from Frank von Delft.

In terms of adding the value to the database, from one of our developers:

I expect that if it's added to <AutoProcScalingStatistics><scalingStatisticsType>overall</scalingStatisticsType> section as <res_i_sig_i_2>value</res_i_sig_i_2> it might just work. We calculate this value using dials.estimate_resolution for xia2 and autoPROC and append it in zocalo to the overall scaling stats read from XML before sending to ISPyB service to write to the database.

@CV-GPhL
Copy link
Author

CV-GPhL commented Dec 4, 2023

I don't see values for any other pipeline than xia2 dials at the moment ... maybe it doesn't yet work for autoPROC?

It should be easy for us to provide that information as well (since MRFANA does exactly this kind of statistics as well - also with some curve fitting and equal-number binning - so dials.estimate_resolution looks very similar to our approach and should be equivalent).

I guess the addition of the "res_i_sig_i_2" is item is quite undocumented and ad-hoc (to make something work) ... as usual in the ISPyB-XML world ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants