Replies: 9 comments 4 replies
-
For example:
|
Beta Was this translation helpful? Give feedback.
-
Suggestion from @stanlo229: Use "building construction" (🏗️) or "inbox tray" (:inbox_tray:) (maybe preference towards 🏗️). So this would look like:
Or:
Following up on this, I think a benefit of 🏗️ over 🦾 is that 🦾 may be more likely to be confused with a different topic than sample transfer, e.g., automation in general. |
Beta Was this translation helpful? Give feedback.
-
Some other thoughts:
Other separators
|
Beta Was this translation helpful? Give feedback.
-
@stefanbringuier, @stanlo229, and @kiranvad, curious to get your thoughts on this. I'm leaning towards this configuration. Emoji Key
Example
|
Beta Was this translation helpful? Give feedback.
-
@sgbaird I love what you’ve done here. My favourite has to be the same emojis but I prefer “/“ as the separator because “|” reminds me too much of the “or” symbol in logic / code. “/“ makes it look like it’s different parts. Perhaps even “>” could be a separator because it points to the next stage of the SDL? |
Beta Was this translation helpful? Give feedback.
-
@sgbaird I really like this! Here is my take on some.
So an entry with semi-auto behavior, would look like:
For experimental planning, I could also see using 📊 or 📆, but 💻 is better. |
Beta Was this translation helpful? Give feedback.
-
For now, going with the following schema, a slight mod to #15 (comment) in light of other comments. Putting the pipe at the end helps to draw the eye towards the text, which was hard to do without any symbols elsewhere.
Subject to change and still open to feedback. |
Beta Was this translation helpful? Give feedback.
-
With the industry cloud lab examples, it's a bit tougher. These labs cater to a much wider set of capabilities; however, often manual sample transfer is at play. Also, automated modules might be used for some procedures while other procedures may require manual steps. There's also some ambiguity when it comes to the software since it's generally proprietary and would likely require human input at various stages in the loop (even if just clicking/confirming). |
Beta Was this translation helpful? Give feedback.
-
Follow-up: should there be some representation for simulations being run (e.g., in addition to experiments)? |
Beta Was this translation helpful? Give feedback.
-
#5 got me thinking about this. There are examples where human intervention is very minimal or only a single step (e.g., transferring a sample) that I want to include.
I've been thinking about how I can either restructure or modify the presentation to capture this.
This got me thinking about emojis, similar to the starred lists that I use.
While the following are applicable, it doesn't allow for any in-between.
🦾 vs. 💪
🤖 vs. 🧑
If there were clearly defined levels of autonomy like with cars we could put the number 1️⃣ 2️⃣ ...
We could also clarify which aspects are autonomous. Some possible categories and emoji are:
So fully autonomous might look like:
🧪/🔬/🦾/💻
Maybe partial would be:
🧪/🔬/❌/💻
Beta Was this translation helpful? Give feedback.
All reactions