Currently, this is defined only for arrays, but it seems like we should have

normalize(x::Number) = x / abs(x)

(I just came across this when trying to implement this algorithm for random unitary matrices, which is basically Q * Diagonal(normalize.(diag(R)), but I discovered that normalize didn't work.)

If there is a nit identified on a PR, an inconsequential change that could be made but is maybe not worth the extra test cycle, enter it here.

If you have a PR that can include one of these changes, mark it as done and add the PR reference after it, in braces

TODO

• keep illegal as _illegal {#23154}
• incase -> in case in factorials.py identified in #23121

Is your feature request related to a problem? Please describe.
The Problem with the current implementation is that it seems fixed for the distance to the Moon. We operate Satellites in geostationary orbit and it would be interesting to see the umbra/penumbra based on the distance to those satellites to assess when they enter the shadow during eclipse time (March-April/September-October).

Cosmology can now read and write to files.
It would be nice to register with Cosmology.write a method for exporting a Cosmology to a HTML table.
There are good examples of IO with Cosmology at https://github.com/astropy/astropy/tree/main/astropy/cosmology/io
and documentation at https://docs.astropy.org/en/latest/cosmology/io.html#cosmology-io

I'm thinking the write_html(...) method

Version of Singularity:

3.0.3

Expected behavior

Some progress or update information during the creation of the SIF file.

Actual behavior

During "Creating SIF file..." step, the console does not produce any visible output for the user - but does create the resulting file eventually.

Steps to reproduce behavior

I was executing a few “larger” builds through the bui

What is the feature ?

I'm trying out this library for the first time and there's some places where it would be delightful to have shorthand functions:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. Currently, lots of boilerplate is required for e.g. white-on-black plotos
   • a cool start would b

import pint
ureg = pint.UnitRegistry()

-140 * ureg.degrees == 220 * ureg.degrees

return False. Is it possible for it to return True instead?

xref xarray-contrib/pint-xarray#119

As of now, there is no measurement for the player's total storage capacity in the editor.

Implementing this should grant players an increased awareness of the impact of parts on storage, as well as how much they currently possess, which can be pretty important.

🙋 Feature Request

🔦 Context

If you paste in a t.co link, or whatever, it should follow it.