libcosim icon indicating copy to clipboard operation
libcosim copied to clipboard

OSP C++ co-simulation library

Results 67 libcosim issues
Sort by recently updated
recently updated
newest added

FMI 3.0 has been out for a long time, and FMI Library now has (alpha level) support for it too. We should start working towards supporting it. I propose a...

enhancement

This feature is desired in the [OptiStress](https://www.sintef.no/en/projects/2023/optistress/) project, where we will need to simulate the same system many times in a loop with parameter variations. It will save a lot...

enhancement

Required for #757. The following features are needed: - [x] functions to save, restore, and delete subsimulator states, corresponding to `fmi2{Get,Set,Free}FMUstate()` - [ ] functions to serialise and deserialise subsimulator...

enhancement

Hei OSP maintainers, I joined DNV earlier this year and have been surprised a couple times with folks occasionally still using the master-slave terminology, which I heard is being used...

Currently, we only do CI builds using GCC 9 on Linux. To make life easier for our users, we should expand the compiler selection and host a greater variety of...

enhancement

# NEED It should be possible to choose the step scheduling type, among at least full parallelism (legacy code), and cascading parallelism. The current chosen mode in the OSP is...

enhancement

# NEED It should be possible to configure the step scheduling type, among at least full parallelism (the default one), and cascading (waterfall effect) parallelism, in the OspSystemStructure.xml file. #...

enhancement

…ks ok, but output variable dispatch bug: mutex issue? taskflow is a thirdparty library: is it the right way to include it?

Steps to reproduce: Create an OspSystemStructure.xml with a simulator source URI e.g. `proxyfmu://localhost?file=Spring.fmu` . This runs fine on Linux but crashes on Windows

bug

Both `slave` and `async_slave` have an `end_simulation()` function, but the higher-level and aggregate classes `simulator`, `algorithm` and `execution` do not. Instead, the lower-level `end_simulation()` calls are triggered by their destructors....

enhancement
discussion needed