Epsilon3 Changelog #2: Submit Your Payload, Procedure Linking, and Warnings
Our next Epsilon3 rocket is launching in 5 days, and we just discovered 40 spare pounds of capacity. Do you have a payload you want us to launch? Has your dog ever wanted to go to space?
Read below about the (other) latest Epsilon3 product updates. We’d love to hear from you about what you love and what else you need.
New: Procedure Linking
Link your procedures together to embed repetitive workflows or anomaly jumps
Link to a specific procedure section directly or all sections within a procedure
After completing a linked procedure, it’s easy to return to the source procedure with a single button
New: Notes, Cautions, and Warnings
Add notes, cautions, and warnings to important steps in your procedures
Enhance the operator experience by highlighting critical details like safety precautions
New: Name Your Operations
Add an operation/mission name to a procedure while running
First step towards tagging capabilities (more to come later)
We heard from numerous teams the need to identify which operation they ran a procedure for, so we added that functionality. Please let us know how you like it!
Improvements:
UI design revamp began with improved visuals for running and previewing a procedure
New! Steps can now be reordered with drag-and-drop handles to make editing procedures easier.
Fixes:
Fixed a user-reported bug where the timing field cut off at 13 characters
Fixed a rendering issue when displaying certain COSMOS command results
Fixed an issue to ensure proper saving of inputted data while running a procedure
Fixed a permissions issue related to disallowing sending commands as a “Viewer”
Fixed an issue where telemetry would stop being rendered in some cases
Fixed a rendering issue to display properly updated results when evaluating Python expressions
Fixed an issue that limited the maximum number of procedures and running procedures displayed on the dashboard
Interested in learning more? Click below to get started.
