-
For humanMine to be a success, we need to take data provenance seriously. Scientists need to be able to reproduce their results and know which versions of data was loaded.
`DataSet.version` should be…
-
Creation date / version ID / general provenance for each derived dataset
d-v-b updated
4 years ago
-
- [x] LdpCreator (per create_base and using the graph from Triannon::Annotation ...)
- [ ] LdpLoader
- [ ] LdpMapper
basically: create, read, update ...
-
ich #242 is solved and its clear whether the reversion plugin is creating useful provenance data we need to come up with views that allow useful interaction with the provenance data
-
(Discussion could apply to any machine)
At NERSC, on pm-cpu/pm-gpu, we currently save timing/provenance data for any job (*) that is using the following allocations:
```
e3sm,m3411,m3412
```
…
-
- Set up a provenance store (database) suitable for the HyperFlow provenance model
- Implement "flushing" provenance events logged during workflow execution to this store
- The store needs to support…
balis updated
6 years ago
-
See [README.md.](https://github.com/x-atlas-consortia/donor-metadata/blob/main/README.md)
-
Iterative algorithms can have very long histories. Maintaining how we obtained final results in the scheduler can become very expensive.
```python
x = 1
for i in range(100000):
x = c.submit…
-
This issue is part of the Strict Provenance Experiment - https://github.com/rust-lang/rust/issues/95228
On some platforms it makes sense to just take a hard-coded address, cast it to a pointer, and…
-
We use "provenance" vs "provenance attestation" inconsistently. We also sometimes use a bare "attestation". We should be consistent throughout the spec.