During the time when github was down we found this bug playing around as free golems. But I believe it could work anywhere even on station.

Testmerges:

Should these just be the same (ideally with the same code)? They are fairly similar, but with some difference, most notably the green/red in the equipper, and the list of stats in the info screen (which includes things like Cloaking and Nebula Resistance that are not visible on the equipping screen).

The minimum elevation setting only applies to predicted passes. It would probably make sense if it would also apply to the polar view and the passes in the radio and rotator controllers.

• "just"
• "simply"
• "obviously"
• "of course"
• "easy"

Inspired by https://twitter.com/AdamChainz/status/1256202405311655938

Right now menus just go 'pop' and appear, and then pop and disappear.

Some quick sliding/appearing animations and VFX would go a long way.

Today's JSON explanation var content:
"The Crab Nebula is cataloged as M1, the first on Charles Messier's famous lis"

The original text is much longer...

Here, the Transfer ID timeout is set to be 1 second:

https://github.com/UAVCAN/libuavcan/blob/f99907251859d7e8dee54f71a19bd80c9b0c64c9/libuavcan/include/uavcan/transport/transfer_receiver.hpp#L24

The spec (both v0 and v1) says it should be 2 seconds by default, although it also could be changed by the application if necessary. We should change it to 2 seconds and possibly add a method to mak

currently the sphinx docs do not list all of the spice functions in the toc, adjust the toc depth in the docs may fix this issue.

At least some of them:
incorrect position, looks like observer is between Pan and Saturn:
cel://Follow/Sun:Saturn:Pan/2019-09-24T01:26:11.75726?x=hd+WcfE8/////////////w&y=78R92Y9s&z=vSGwz0QwAw&ow=0.996460612057&ox=0.0030448977001&oy=0.0752197931511&oz=-0.0374026728395&track=Sun:Saturn&select=Sun:Saturn&fov=40.0&ts=100.0&ltd=0&p=1&rf=3973015&lm=0&tsrc=0&ver=3

absolutely incorrect, that time Su

We should add a page to the documentation describing the space weather methods for accessing / comparing indices, as well as one for the model_utils tools.

It's possible (and tested) to slice an arbitrary set of indices off a dimension:
b.slice(1, [2, 3, 5])

But this isn't documented.