Tag Info

That isn't what you said earlier. You said that those were means, not slopes. As for ease of use... A proper implementation in Excel would be a nightmare to maintain given the necessary complexity of ...

yeah the constant values of system A are essentially the "slopes" (of the fit function) of each sections. With that in mind and the point data; I think maybe the grey fit was done with least-...

This is a severe case of underfitting. The curve is far too smooth, and essentially ignores many of the important features of the data.

The answer is any solver that supports integer variables. This is because either the solver has native support, or JuMP will reformulate the problem into an equivalent problem supported by the solver.

Any solver needs to be aware of a cost function that takes into account the spans of each mean, the locations of the point-like data, and a smoothness cost that can be defined by a second-order ...

This is possible in Excel using the TREND or LINEST functions. However, the presented data is not entirely consistent, so the function has to average them in some way. Is it supposed to be one smooth ...

I don't think that you should attempt to reproduce that method exactly because it seems wrong to me. Observe the last blue "bump" - the grey curve does not respect that mean. Excel is not ...

Extensometers: As you mentioned blue is System A Set 1, orange ist System A Set 2. System A measures the deformation over its built-in length. That means you get constant deformation values over their ...

If you used a binary distribution, it might have been already compiled with that setting on; I think it is referred to as "parascip" - I see on the download page some versions say "no ...

Can you describe what the blue (set 1?) and orange (set 2?) curves are, what the points mean (wire strain?), and the method used to perform fit of the grey curve?

Are they seriously asking the user recompile the whole program to enable multi-core usage?!

The CPU maxing at 10% while solving a complex computational job might be an indication that your code runs single-threaded. Please verify that you have enabled concurrent solving mode in SCIP, see ...

Use resource OS monitor to see what is being maxed out. It sounds like it is running as a single thread on one performance CPU (or is heavily IO bound). You may get more informed answers on the JuMP ...

Another physical resource of your system is probably causing this. Use a monitoring tool to find out, if memory, disk or network are overloaded. In case you have only a small amount of memory, the ...

Try HiGHS, it supports semi-continuous variables: using JuMP using HiGHS # solver that supports Semicontinuous range model = Model(HiGHS.Optimizer) @variable(model, x in Semicontinuous(2.0,100.00)) @...