-
Notifications
You must be signed in to change notification settings - Fork 0
SPEC data file is in wrong directory now #408
Comments
I do not think this is fixed yet, last data set on screen is SAXS S16 Qu09, we collected 100 SAXS scans in the mean time (I was fixing my computer). Anyway, something to look on Thursday if you have time. |
scan logs are not updating, last entries:
but livedata page says
|
Our intention is this table:
|
Confusing, Did you change anything? WAXS graphs are coming out. |
newUser?
…On Tue, Sep 15, 2020, 9:40 PM Jan Ilavsky ***@***.***> wrote:
Confusing, Did you change anything? WAXS graphs are coming out.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#408 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARMUMHPJS23VB5FQ3Q7PWLSGAQTDANCNFSM4RN7QW4Q>
.
|
Live data page shows only SAXS and WAXS when running from spec, which is what we need to do for now for more complicated experiments which talk directly to motors. Note, that in spec we will have different location of spec file than in BS, I am not sure how to move file in spec. I will ask jeff if he can help me to make a change to follow BS logic. For now, this is what spec collects:
|
Interesting, plots SAXS and WAXS data. But Flyscan data are in the logs. |
Looks like Jeff will modify the code in spec to arrange data same as BlueSky. I will test tomorrow. |
Meanwhile, the scanlog is logging the Fly scans now and livedata (known problem) is not plotting them yet.
|
In these logs, the SPEC data file
|
The SPEC data file reports FlyScan NeXus/HDF5 files are stored in subdirectories according to the new plan:
|
These are the most recent files in that subdirectory:
The file These files are written when SPEC is used. We can tell that by looking at the first lines of the SPEC data file: SPEC writes the file:
Bluesky writes the file:
The ONLY thing that SPEC needs now is to write the data file in the |
Assuming Jeff makes the code change, I will test this: |
We also need to (re)confirm that Bluesky uses and reports the new directory scheme for step scans and fly scans. |
I have fixed the file location iss spec. There are few wrong attempts. Will send some details using teams. |
Much better too document those details right here.
…On Thu, Sep 17, 2020, 10:35 AM Jan Ilavsky ***@***.***> wrote:
I have fixed the file location iss spec. There are few wrong attempts.
Will send some details using teams.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#408 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AARMUMFTGY6HBFGE3EPTZCLSGIUEFANCNFSM4RN7QW4Q>
.
|
Not if user names are involved. |
I am confused about record in scanlog for live data page. SAXS and WAXS are wrong now. FLyscan is correct. How is the log filled, what does it use? Obviously, I broke something by fixing the paths and do not know what to fix now. |
I think I got it. it is using 9idcLAX:specFile and that needs to contain path to spec file... I can fix that. |
Bluesky-directed FlyScan now plots correctly in |
Once we are confident that Bluesky's USAXS step scans will plot properly with livedata, this issue can be closed (again). |
I believe |
Basically, getting |
Last two comments belong in separate issue if you agree. |
Scans in these directories have SPEC, Bluesky FlyScan, and Bluesky step scan variations, respectively. Same sequence for each.
|
I'll look at the |
I think this was fixed. We need to test this. I think spec was changed to follow BS template - "spec" file inside user folder. |
Seems to be fixed |
SPEC data is in the wrong directory. Scan log says
/share1/USAXS_data/2020-09/09_15_Qu/09_15_Qu.dat
but file is not there. It's in the parent directory (the current working directory). Need to fix that ASAP.The text was updated successfully, but these errors were encountered: