-
Notifications
You must be signed in to change notification settings - Fork 3
create data export example #33
Comments
These are the contents of the sqlite directory just after the exception:
|
There is only one data column with "NFS" in it. Seems be trouble creating ophyd object names with the data column names that have embedded whitespace. These names come from the text in the scaler channel labels. It was OK to acquire data with such names. Looks like an assumption bug to me in the export code. Either of these places:
|
@tcaswell : FYI only. In a recent zoom meeting, I mentioned previous problems trying to move data between two mongodb servers for databroker. You emphasized the importance of reporting problems. This issue records part of that problem, which continues to sit untouched. Not sure this ever rose to the level of bug report since I was learning at the time. Since there is renewed attention on moving data between databroker instances with the Pilot project, this could follow that effort. |
So, still not a problem to be fixed but rather a procedure to be determined. |
Follow this comment for 4-ID-C Polar,
Other search criteria are possible, using the mongodb-query language. |
This command was a successful export:
Now, what about in a jupyter notebook? |
No notebook example here, the python API looks complicated, in favor of command-line tools. Maybe a markdown page showing how to use the command-line tools. |
See the documentation for instructions to pack and unpack. The documentation addresses the copy from broker to broker using the command-line tools. |
Create an example notebook showing how to move scans from from broker to another using the Broker API.
Related to a need at APS 3-ID-D
The text was updated successfully, but these errors were encountered: