Open sgbaird opened 2 months ago
This primarily is geared towards module 4 and 5 from https://ac-microcourses.readthedocs.io/en/latest/courses/robotics/overview.html#modules
Hey @sgbaird , just a few questions.
Some examples:
I'm still working out a few details on what device pages should contain, but it should have some kind of brief intro to what the device is, links to the original websites and documentation (e.g., like the links above), a short description of why this is relevant to scientific lab automation, a link to the corresponding accelerated discovery post, and links to related code within the AC Training Lab repo.
The intent is to not replicate existing documentation, but link out to it where possible, and clarify any differences or specifics to the current demo.
I think Yang is going to make an accelerated discovery post to start out since he was working on it a bit before, and that will be used as a sort of hand-off to you.
Adding some of this to https://ac-training-lab.readthedocs.io/en/latest/contributing.html
@gursi26 you can go ahead and make the Accelerated Discovery post (here are examples: https://accelerated-discovery.org/tag/ac-training-lab).
I have made the post, should this issue be closed (unless you also have something else in mind)?
Just saw - nice! https://accelerated-discovery.org/t/making-the-mycobot-280-accessible-over-mqtt-in-a-hugging-face-space/430
Any thoughts on what a "device page" might look like? This idea isn't fully fleshed out. Curious to hear your opinions (the idea being a focus on replicability)
Since the LEGO connectors can be a pain and a bit flimsy, I flipped the base and used a 3 mm Allen key to screw the embedded screws into the cobot (4 internal screws). Much more stable now, without having to put lots of Lego connectors and make it really difficult to get off.
Not sure what we'll want to do when we're thinking about the MyAGV, but shouldn't matter for now.
Unfortunately it's neither particularly stable nor very well centered (i.e., the benefits of extra clearance as a "pedestal" are not exactly realized). Not sure if it's worth using these. May come in handy for another demo.
For a device page, would a README in src/ac_training_lab/cobot280pi/
be the appropriate place to put it? I have a set of setup instructions I wrote down while I was setting up the second cobot.
The original intention was to have these in https://github.com/AccelerationConsortium/ac-training-lab/tree/main/docs/devices and have a "devices" drop-down on the left sidebar or similar. I hadn't considered putting it in src
as much. Thoughts on the two?
Yep, either is fine, Ill add the markdown file to that directory in my PR.
Based on the following demo videos by Yang: https://www.youtube.com/playlist?list=PLKFxDV1Aoxg7gdBsbIH7mB6FjYu3F57uj
Add an Accelerated Discovery post related to this and a device page.
Likely based on the following docs:
I believe Yang mentioned he primarily used blockly when he was testing things out - should be a one-to-one correspondence in terms of Python functions.
Yang also mentioned watching some videos:
From here on, the bulk will likely be directly in Python: https://docs.elephantrobotics.com/docs/gitbook-en/7-ApplicationBasePython/.