You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the system indexes an "experiment" which was a nice idea but really only good for a demo. While the concept of "experiemnt" may live on, what that model looks like is a little unclear.
One thing is clear, though. Splash is going be consuming bluesky runs as the principal place to store "run" data...loosely defined as the stuff that gets store for each trial in an experiment. https://blueskyproject.io/databroker/v2/user/index.html
There is a well-defined schema for a set of document types in the bluesky event model (https://github.com/bluesky/event-model/tree/master/event_model/schemas). We will get a lot of useful functionality out of these documents if we index the run_start documents in elastic as they come into mongo.
The end goal is to make it easy to search for a run based on several fields of particular interest (but not exclusively):
time
user
bealline_id
sample
detectors
So, this task is to set up create the stuff in splash-deploy that us perform smart searches (fuzzy, suggestions, etc) on those fields in start documents.
The text was updated successfully, but these errors were encountered:
Do you have a pull request? Note that if you create one, you can reference this issue in the comments and github will auto-close this issue when the PR is merged.
Currently, the system indexes an "experiment" which was a nice idea but really only good for a demo. While the concept of "experiemnt" may live on, what that model looks like is a little unclear.
One thing is clear, though. Splash is going be consuming bluesky runs as the principal place to store "run" data...loosely defined as the stuff that gets store for each trial in an experiment. https://blueskyproject.io/databroker/v2/user/index.html
There is a well-defined schema for a set of document types in the bluesky event model (https://github.com/bluesky/event-model/tree/master/event_model/schemas). We will get a lot of useful functionality out of these documents if we index the run_start documents in elastic as they come into mongo.
The end goal is to make it easy to search for a run based on several fields of particular interest (but not exclusively):
time
user
bealline_id
sample
detectors
So, this task is to set up create the stuff in splash-deploy that us perform smart searches (fuzzy, suggestions, etc) on those fields in start documents.
The text was updated successfully, but these errors were encountered: