Should dials.import run dials.show at the end #1591
Replies: 4 comments 1 reply
-
I would say not, because at the moment I get useful information such as the geometry overrides and the Format used for import all in one screen:
|
Beta Was this translation helpful? Give feedback.
-
The complement of this viewpoint is the case where a user is not overriding anything:
Some subset of this information would help to give a summary of what you have imported...
on a practical note, just printing the scan info for each sweep would be useful. I appreciate not showing the full |
Beta Was this translation helpful? Give feedback.
-
Alternatively: I feel like the most common case is users not overriding parameters but I recognise that could be a local perspective. |
Beta Was this translation helpful? Give feedback.
-
Multipanel detectors make dials.show pretty verbose :)
…On Thu, Feb 11, 2021 at 8:11 AM David Waterman ***@***.***> wrote:
I agree some limited additional output could be useful. I don't really see
the point of replicating the whole dials.show output, but agree maybe a
little more detail than
num images: 50
sequences:
still: 0
sweep: 1
num stills: 0
could be helpful
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1591 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADGY5SR72MXYJWNUYVK3BQTS6P6T3ANCNFSM4XO2PYLA>
.
|
Beta Was this translation helpful? Give feedback.
-
i.e. to usefully show what was imported?
Beta Was this translation helpful? Give feedback.
All reactions