The following:

.box {
  border-top-left-radius: 10px;
  border-top-right-radius: 20px;
  border-bottom-left-radius: 20px;
  border-bottom-right-radius: 40px;
}

is currently minified to:

.box{border-top-left-radius:10px;border-top-right-radius:20px;border-bottom-left-radius:20px;border-bottom-right-radius:40px}

but could be “short-hand”ed:

.box {borde

the example at page https://julianlsolvers.github.io/Optim.jl/stable/#algo/complex/ fails.
the environment is:

• julia 1.1.1
• IJulia v1.20.2
• Optim v0.20.0

minimal (not) working example from the docs of the page linked above:

using Random, LinearAlgebra, Optim
Random.seed!(0) # Set the seed for reproducibility
# μ is the strength of the quartic. μ = 0 is just a quadratic problem

I think the examples needed more structure for some time. Now with the binder support, it seems like a good time to make these adjustments:

• https://pypsa.readthedocs.io/en/latest/examples.html
• https://pypsa.readthedocs.io/en/latest/quick_start.html

Adding "MC" or "Monte-Carlo" to labels of Monte Carlo optimisation plots. Easier to distinguish it from the Efficient Frontier output.

Problem description

in our YAML files, we can only handle loading timeseries data if the data is formatted as e.g.:

resource: file=filename.csv or resource: file=filename.csv:columnname.

Referencing the file as follows will cause the data to be loaded in as a string without a timeseries dimension (and an exception will be raised on running the model):

`resource: file = filename.

Similar to the current ones available for Mac OS I would like to provide a similar installation and run experience on Linux.

For users and potential developers of Modelica library, I think that we need to do the effort to integrate the documentation in each class/block/model with the annotation function. You know, the documentation must be where they expect to be. Otherwise, people miss part of our work. I'm sure to this task is tedious, but the result looks very nice.