Comments (3)
I sketched out the old and new (with a single event, multiple events would make more use of the slice object)
Here's a suggestion as to how it could be implemented.
- StreamDatum
- no
datum_kwargs
- no
stream_name
, instead a pointer to the Descriptor it provides some or all of the data_keys data_keys
list to show which data_keys of the Descriptor it providesseq_nums
is aslice
object showing the Event numbers it corresponds toindexes
is aslice
object passed to the StreamResource handler so it can hand back data and timestamps
- no
- Event and EventPage
- external
data_keys
will be missing fromdata
andtimestamps
- external
The Event side of the diagram then becomes optional, if all detectors write external files then there will be no Event documents
@tcaswell @danielballan shall we begin writing this?
from event-model.
Yes, I think so. I'd like to do this in tandem with @DiamondJoseph's NeXus writers and a sketch of our proposed new storage model for Databroker to validate that everything works out the way we expect.
from event-model.
Can delete stream_names from StreamResource too
from event-model.
Related Issues (20)
- Store document uuids before executing callbacks in RunRouter
- Adding support for detailed and structured data types HOT 16
- Add new document for "bulk" external resources HOT 6
- jsonschema.__version__ deprecation warning
- Proposal: remove restrictions on some RunStart document keys HOT 2
- range in `data_keys` HOT 7
- Python minimum version/using 3.8+ features HOT 6
- UserWarning: 'bulk_events' has been deprecated in favor of 'event_page', HOT 1
- Add typing support to event_model HOT 9
- Convert event-model to use the dls python skeleton HOT 5
- Linkcheck job wrong
- Sort existing schema alphabetically
- Allow event counters to be defined outside of a run
- Slight difference between the current bluesky bundler and event model HOT 2
- Switch from `partials` to Compose classes HOT 1
- Use the python skeleton's version determination method
- Reorder the schema for easier review
- Investigate independent versioning for schema HOT 1
- Add a unit test for schema rejecting dots in keys
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from event-model.