Closed prjemian closed 1 week ago
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
In general, I find some of the markdown comment difficult to find in the middle of the code cell output, like below; maybe adding bullet point or a <br>
before the comment would help.
Not sure what that bug was in the last few suggestions. It was displaying the correct sentence before pressing the green button, but then showed the code for an image as the original...
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.08% |
Covered Lines: | 1021 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.08% |
Covered Lines: | 1021 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.08% |
Covered Lines: | 1021 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.08% |
Covered Lines: | 1021 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
@rodolakis I believe this is ready for review again.
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
OK so this is what I was trying to suggest:
It looks good in preview, but when I click "add review comment" it becomes wrong (quoting the giant image code instead).
In general, for all 3 sections, I would replace the sentence:
Step scan a motor (m1) and measure 3 (as configured above) images at each step. Also record total counts and the maximum counts value for each step.
With a bullet point sentence:
I would write instead:
Both motors, m1
and m2
, move at the same time. Below is a plot showing the readback values of each motor during a two-motor scan
versus the data point number:
The file name, as the catalog will find its image contents, is reconstructed:
I am not sure I understand this sentence. I was proposing:
"The catalog uses the file name to locate and retrieve its image contents. This file name is reconstructed as follows:"
"The second motor of the
grid_scan
(m2
) is snaked. It's direction changes with each subsequent increment of the first motor (m1
). Here's a plot of readback value of each motor from agrid_scan
plotted v. data point number:\n",
I was proposing:
During the grid_scan
, the second motor (m2
) moves in a snaking pattern: its direction changes with each subsequent increment of the first motor (m1
). Below is a plot showing the readback values of each motor during a grid_scan
versus the data point number:
I was proposing instead:
All along, quietly in the background, the data has been saved both to a catalog and to a SPEC data file. The total counts, max counts, and unique ID from all scans can be plotted from the SPEC file using PyMCA or NeXpy.
The image content is not stored in the SPEC file, so images cannot be viewed from it. However, references to the images are save as comments. See the comment lines that match a search for
resource {'spec': 'AD_HDF5'
@prjemian I rewrote my broken comments. I still cannot quote anything as a github "suggestions" past a certain point in the document (only works at the beginning of the notebook for some reason)
@rodolakis : I believe I have responded to all your comments. Thanks for the thorough review.
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
All good. Everything has been resolved as far as I am concerned except for one minor formatting suggestion (I tagged you on it). So minor that I'm fine with merging with or without.
@rodolakis Thanks!
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Totals | |
---|---|
Change from base Build 9506811548: | 0.0% |
Covered Lines: | 1020 |
Relevant Lines: | 1226 |
@sureshnaps, @qzhang - Can you examine this notebook? It can guide you during commissioning activities.
Start here: https://bcda-aps.github.io/bluesky_training/howto/_ad_v_motors.html#The-(1-D)-bp.scan()-plan-with-one-motor