Jose Daniel Lara

Are these on native M1 or with Rosetta?

Shouldn't this problem be solved with the definition of `hypot` in `DiffRules.jl`? https://github.com/JuliaDiff/DiffRules.jl/blob/5a121b8ccb996525824160fc822c2a69d172662c/src/rules.jl#L86

I think this is partially fixed here: https://github.com/SciML/OrdinaryDiffEq.jl/pull/1105

@AbrahamAlvarezB we don't have a great way to do slicing at the moment. Since we implemented the code to optimize a single value or single column fetching we never implemented...

@andrewrosemberg what you describe falls into capabilities that control individual components, where we can identify 3 uses cases at least 1. System has component X with a Time Series A...

I think we should document this behavior better to avoid annoyances from the users.

I don't think that is guaranteed in PowerSystems that this will return the same thing ``` for g in get_components(ThermalStandard, sys) rl = get_ramp_limits(g) set_ramp_limits!(g, rl) end ``` depends on...

@daniel-thom and @nickrobinson251, I implemented a mechanism to read data from PSSe 30 in this PR. I only have a small test case to validate the fields but this is...

This PR requires and equivalent refactor of PSB to make it compatible with the StandardLoad parsing.

Currently, PSS 34 doesn't support these models yet