Miles Cranmer

This is not yet possible but will likely be soon; @gca30 is working on this feature

The goal was within the next 6 weeks or so but @gca30 has been pretty fast so might be earlier 🙂

Hi @Deduction42, Just to ask, why not just define a converter to SI units for your own work? So, my sense is that adding this capability will complicate everything about...

I see, thanks. Yeah if it is just the import and export, I definitely think it's easier and is a possibility to include. My main objection is actually doing processing...

> But wouldn't it be simpler to define a SymbolicDimension as a regular Dimension times a scale? This is similar to how it works. The long sparse vector is needed...

There is a known high-severity CVE for the VSCode Python extension: - https://github.com/advisories/GHSA-36jr-8w83-wr8q - https://nvd.nist.gov/vuln/detail/CVE-2024-49050 This was patched by [v2024.20.0](https://github.com/microsoft/vscode-python/releases/tag/v2024.20.0). However, the current version of Cursor is stuck on an...

Argh, sorry this doesn't work. It's bad that the docstring suggestion is broken. In the meantime, the "standard" way to convert to symbolic units is to use `|> us"kg"`. So...

Oh I see. I don't have a function for this, because I thought it would never be needed (symbolic units are mainly just for display). Could I ask what the...

Actually it seems like this works: ```julia julia> x = 5u"kg" 5.0 kg julia> convert(Quantity{Float64,SymbolicDimensions}, x) |> typeof Quantity{Float64, SymbolicDimensions{FixedRational{Int32, 25200}}} ``` still it would be interesting to know the...

> But they should also be able to override the unit that should be displayed, in both formats, symbolic or not I think the part I'm not understanding here is...