Comments (6)
I would additionally include a hardcoded, not resettable ID that is incremented / uniquely generated for each run and therefore without doubt identifies each run (even if the other IDs are sometimes messed up). Errors happen and this allows to track runs even if the other IDs are changed (to fix errors etc).
from planktoscope.
This was improved in part by #67 .
from planktoscope.
So now these id are not automatic anymore and are managed solely by hand.
Eventually, I would like to add a system where the last acq_id
used is shown for the chosen specific sample_id
if this one exists. Same thing for the process_id
.
from planktoscope.
Still, I find it very important to have an additional ID that users can not mess with. Errors do happen.
from planktoscope.
I've added what you suggested @moi90 . There is now a sample_uuid
, acq_uuid
, process_uuid
that are added everytime a new process is run
from planktoscope.
Ah, great!
from planktoscope.
Related Issues (20)
- v2023.9.0-beta.1 has weird interactions between Cockpit, GPS, and system time
- frontend/node-red-dashboard: v2023.9.0-beta.1 Impossible to configure White Balance HOT 5
- os/networking: Simplify network config by replacing dhcpcd with NetworkManager HOT 1
- Use Prometheus instead of Node-RED for system hardware monitoring
- "Expert Setup" instructions in documentation don't work HOT 8
- Optic configuration preview screen blank/black HOT 7
- backend/controller: `raspimjpeg.conf` file has incorrect image size settings which are ignored HOT 1
- backend/controller: raspimjpeg captures overexposed images HOT 5
- docs: planktoscope.org website is confusing with multiple hardware versions HOT 1
- community: Build an initial network of active PlanktoScope users
- community: Build an active community of users who consistently share about how they're using their PlanktoScopes
- docs: Navbar is too cluttered
- hw-enablement: Software is missing a hardware configuration for the v2.6 hardware
- hw-enablement: Focus stepper direction on v2.6 hardware is flipped
- frontend/node-red-dashboard: Incorrect metadata field values for git repo and commit/version HOT 3
- docs: Navbar displays an irrelevant version number HOT 1
- docs: Documentation doesn't explain our hardware+software version numbering system HOT 3
- backend/processing/segmenter: Segmenter crashes with OOM on dense images
- Metadata box in the sample tab for time between sampling and analyze of the sample HOT 5
- docs: Provide a clear path through the docs for users trying to get started HOT 2
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 planktoscope.