fmu-manipulation-toolbox 0.0.dev3__tar.gz

fmu_manipulation_toolbox-0.0.dev3/.git_archival.txt

@@ -0,0 +1,3 @@
+node: $Format:%H$
+node-date: $Format:%cI$
+describe-name: $Format:%(describe:tags=true,match=*[0-9]*)$

fmu_manipulation_toolbox-0.0.dev3/.gitattributes

@@ -0,0 +1 @@
+.git_archival.txt  export-subst

fmu_manipulation_toolbox-0.0.dev3/.gitignore

@@ -0,0 +1,31 @@
+# Python
+__pycache__
+*.pyc
+.idea
+.vs
+.vscode
+# OS
+.DS_Store
+# Compiled binaries (not committed except the pre-built resources)
+*.dll
+*.exe
+# Build outputs
+dist
+site
+remoting/out
+remoting/build
+container/build
+container/build-win64
+container/out
+container/.vscode
+# Locally built darwin binaries (shipped via CI artifacts, not committed)
+fmu_manipulation_toolbox/resources/darwin64/client_sm.dylib
+fmu_manipulation_toolbox/resources/darwin64/container.dylib
+fmu_manipulation_toolbox/resources/darwin64/server_sm
+tests/tmp/
+tests/.coverage
+tests/.pytest_cache/
+tests/coverage.svg
+
+# Version file generated by setuptools-scm
+fmu_manipulation_toolbox/_version.py

fmu_manipulation_toolbox-0.0.dev3/CHANGELOG.md

@@ -0,0 +1,347 @@
+# FMU Manipulation Toolbox changelog
+This package was formerly known as `fmutool`.
+
+# Upstream
+* FIXED: text files are written and read in UTF-8 on every platform: assembly descriptions (CSV, JSON),
+         the port names CSV (`-dump-csv`, `-rename-from-csv`), `container.txt` and `datalog.txt`, and the log
+         saved by `fmutool-gui`. They used the platform encoding, cp1252 on most Windows installations, so
+         a non-ASCII name written on one platform was misread on another. A UTF-8 byte order mark (added
+         by Excel) is accepted, and a file that is not UTF-8 is still read with the platform encoding,
+         with a warning.
+* FIXED: reading an SSP archive: the elements of `SystemStructure.ssd` are recognized by their namespace
+         (SSP 1.0) instead of the literal `ssd:` prefix. A valid SSD using another prefix or a default
+         namespace failed with `AttributeError`. An invalid SSD (other namespace, not well-formed,
+         reference to an unknown element) now raises `AssemblyError` with a clear message.
+* REMOVED: `ModelStructureCounter`. The Model Exchange sizes are computed from the descriptor tree by
+         `ModelDescription.model_exchange_sizes()`. `OperationSummary.structure` is replaced by
+         `OperationSummary.number_of_continuous_states` and `number_of_event_indicators`, which
+         `EmbeddedFMU` already provided.
+* CHANGED (**breaking**): `fmutool`, `fmucontainer` and `fmusplit` exit with positive codes, shared by
+         the three tools: 2 invalid command line, 3 input missing or unreadable, 4 invalid input,
+         5 operation or build refused or failed, 6 output cannot be written, 7 `-check` found the FMU
+         non-compliant (see the CLI guide). They used negative codes (`-1` to `-6`), with a different
+         meaning for each tool. Scripts that test the exact value must be updated.
+* ADDED: `fmutool -check` exits with status 7 when a checker reports an error, so that it can be used
+         in CI. The XSD checker reports every violation instead of the first one only.
+* ADDED: `OperationSemanticCheck`, a built-in checker for the rules of FMI 2.0 and 3.0 that the XSD
+         cannot express: unique names and value references, allowed `causality`/`variability`/`initial`
+         combinations, `start` values, references between variables and in `<ModelStructure>`.
+* CHANGED: an `FMU` parses its `modelDescription.xml` once for all the operations applied to it, and
+         operations declared `read_only` (summary, CSV dump, checkers) no longer rewrite it: the
+         descriptor stays exactly as in the archive.
+* FIXED: `get_checkers()` added the checkers registered through entry points again at each call.
+* FIXED: `fmusplit` failed with `KeyError` on an FMI-3 variable without `causality` attribute.
+* FIXED: `fmucontainer`: the `modelDescription.xml` of the container is now built with ElementTree.
+         Names and descriptions coming from the embedded FMUs are escaped (a `&`, `<` or `"` made
+         the descriptor invalid), and the file is written in UTF-8 as required by FMI 2.0 and 3.0
+         (it declared ISO-8859-1 but was written with the encoding of the locale).
+* FIXED: `fmucontainer`: in FMI-2 containers with profiling, `ts_multiplier` or a Model Exchange
+         solver, `<ModelStructure>` listed local variables instead of the outputs.
+* CHANGED: `FMU` can be used as a context manager (`with FMU(...) as fmu:`), and has a `close()`
+         method. Its temporary directory is now also removed at interpreter exit, and when opening
+         fails.
+* FIXED: opening a file that is not a ZIP archive, or a directory, raised a raw exception instead
+         of `FMUError`. `fmutool` now reports these errors, and an unreadable `modelDescription.xml`,
+         with a clear message instead of a traceback.
+* CHANGED: `fmutool` operations: `modelDescription.xml` is now modified in place with ElementTree
+         instead of being re-generated, so that everything an operation does not touch is kept as
+         is. Fixes text and attribute values written unescaped or unescaped twice (which produced
+         invalid XML, and made the second of two chained operations fail), and the loss of
+         `<Annotations>` of FMI-2 variables, FMI-3 `<Alias>`, all but the first `<Start>` of FMI-3
+         `String` arrays, empty FMI-3 `<Start value="">`, FMI-3 `<Dimension start="1">` (the
+         array became a scalar), comments and the XML declaration (required by FMI 2.0 and 3.0).
+         The descriptor is always written in UTF-8.
+* FIXED: removing ports from an FMI-2 FMU did not renumber the `derivative` attribute, which
+         then pointed to the wrong variable.
+* CHANGED: an operation is now refused with `OperationError`, leaving the FMU unchanged, if its
+         result would break the FMI standard: removing every variable, removing a variable still
+         referenced by a kept one (`derivative`, `previous`, `clocks`, `<Dimension
+         valueReference>`), or giving the same name to several variables (or FMI-3 aliases).
+* FIXED: `-remove-sources` also removes the `<SourceFiles>` elements of the descriptor, and now
+         works on Model Exchange-only FMUs.
+* CHANGED: `FMUPort` is now a view on the descriptor tree. Building a detached `FMUPort()` and
+         `push_attrs()` are deprecated. Operations can reach the whole tree through their new
+         `model_description` attribute. Namespaced attributes are still given to the callbacks as
+         `prefix:name`, but the `xmlns:*` declarations are no longer listed (`-summary` no
+         longer prints them).
+* FIXED: MCP server: invalid arguments are reported with a short, actionable message (unknown option or
+         argument with the list of the allowed ones, missing argument, value outside its constraint)
+         instead of the raw Pydantic text and its documentation link.
+* ADDED: MCP server: **single-FMU tools** beyond container assembly — `summarize_fmu`,
+         `check_fmu` (FMI schema conformity), `dump_ports_csv`, `rename_ports_from_csv` and
+         `apply_operation` (prefix stripping/merging, trimming, regexp filtering). The tools that
+         rewrite an FMU always produce a new file and leave the source untouched.
+* ADDED: MCP server: assembly edition is now reversible and batchable — `remove_link`,
+         `unset_start_value` and `add_links` (bulk wiring, reporting per-link failures).
+* ADDED: MCP server: optional **bearer-token authentication** for the HTTP transport
+         (`--token generate`, or `FMUCONTAINER_MCP_TOKEN`). The loopback interface keeps remote
+         machines out, but not the other processes of the same machine, which can otherwise read
+         and write files through the server.
+* FIXED: `Checker`: XSD validation errors were lost instead of being reported — the error was
+         logged with a malformed `logger.error(reason, msg)` call, which raised at formatting time.
+* ADDED: `fmutool-mcp`: a **standalone MCP server**, launched by the MCP client over the
+         **stdio** transport (Claude Desktop, VS Code, Cline, ...) and requiring neither a display
+         nor a running GUI. It serves exactly the same tools as the GUI assistant, on top of the
+         public `Assembly` API. `--root DIR` (or `FMUCONTAINER_MCP_ROOT`) confines the agent to a
+         directory tree; `--transport http` is also available for clients that attach to an
+         already-running server. The server advertises itself to clients as `fmutool`.
+         Requires Python >= 3.10 and the `mcp` extra.
+* ADDED: `fmucontainer-gui`: **AI Assistant** — the Container Builder can expose its assembly
+         capabilities to an AI agent (e.g. GitHub Copilot in *Agent* mode) through a
+         [Model Context Protocol](https://modelcontextprotocol.io/) (MCP) server. Toggle it from the
+         **Configuration** menu (*AI Assistant On/Off*); the agent drives the live canvas (add FMUs,
+         wire ports, expose inputs/outputs, set start values and options, build the container FMU),
+         with every action marked as an unsaved change and written to the log panel. Port
+         introspection reports every variable with its causality, variability, type, unit, start
+         value and description, and is filterable (by causality or name pattern) and paginated so
+         that industrial FMUs do not saturate the agent context. The server also ships its own
+         know-how, so that any MCP client benefits from it: three prompts (`build_container`,
+         `diagnose_assembly`, `inspect_fmu`) describing complete procedures, and reference
+         resources (`guide://usage`, `fmi://conventions`, `container://options`,
+         `assembly://current`, `fmu://{name}/ports`). Building a container reports its progress
+         to the client instead of running silently, and the time the tools wait for the GUI is
+         configurable with `FMUCONTAINER_MCP_TIMEOUT` (60 s by default, ten times that for
+         builds). The server uses
+         the Streamable HTTP transport bound to `127.0.0.1:8765/mcp` (port overridable with the
+         `FMUCONTAINER_MCP_PORT` environment variable). This feature requires Python >= 3.10 and the
+         new `mcp` extra: `pip install "fmu-manipulation-toolbox[gui,mcp]"`. See
+         [AI Assistant (MCP server)](docs/user-guide/fmucontainer/ai-assistant.md).
+* ADDED: Model-Exchange FMUs: the number of continuous states (`nx`) and of event indicators (`nz`)
+         are now computed from `<ModelStructure>` (FMI-2 `<Derivatives>` / FMI-3 `<ContinuousStateDerivative>`
+         and `<EventIndicator>`, array variables counted per element).
+* ADDED: `fmucontainer`: embedded fixed-step solver for Model-Exchange FMUs. All ME FMUs are advanced in a
+         single container-wide loop so their state derivatives, state events and time events stay consistent
+         across the coupled set. A forward-Euler integrator is used by default, with an RK4 integrator also
+         available. An FMU providing both Co-Simulation and Model-Exchange is now embedded in Co-Simulation mode.
+         Assemblies mixing Co-Simulation and Model-Exchange FMUs are supported.
+* CHANGE:`PySide6` (the GUI toolkit) is no longer installed by default. `pip install fmu-manipulation-toolbox`
+         now only installs the **CLI** (`fmutool`, `fmucontainer`, `fmusplit`, `datalog2pcap`) and the
+         **Python API**, neither of which import `PySide6`. To use the **Graphical User Interfaces**
+         (`fmutoolbox`, `fmutool-gui`, `fmueditor`, `fmucontainer-gui`), install the new `gui` extra:
+         `pip install "fmu-manipulation-toolbox[gui]"`. A convenience `all` extra (`gui` + `test`) is also
+         available. See the [Installation Guide](docs/installation.md).
+* CHANGE: CI improved.
+* CHANGE: Test plan improved.
+
+# Version 1.9.4.2
+* ADDED: Container thread synchronization on macOS now uses a semaphore instead of a barrier
+         (macOS does not implement POSIX `pthread_barrier`).
+* ADDED: GUI: `fmucontainer` FMU detail panel now offers a right-click **Select all** / **Select none**
+         context menu on the *Input Ports* and *Output Ports* tables to expose ports in one click.
+* FIXED: Container datalog: samples are now logged during event handling so the recorded outputs
+         reflect the freshly updated discrete state.
+* FIXED: Container now decodes the `fmuResourceLocation` URI following RFC 3986 (percent-encoded
+         octets such as `%20` are decoded, drive letter handled), fixing resource paths that
+         contain spaces or special characters.
+* FIXED: FMI-3 model icon support: `fmutool`, `fmueditor` and `fmucontainer` builder now read the
+         icon from `terminalsAndIcons/icon.png`, and generated FMI-3 containers store their icon there.
+* FIXED: GUI: `fmucontainer` right-click on a node now first selects the pointed node; "Replace FMU" (Info)
+         also refreshes the tree view.
+* FIXED: Container Event Mode: each FMU is now driven `Set inputs -> fmi3UpdateDiscreteStates -> Get outputs`
+         within the same Gauss-Seidel sweep, so read-back outputs reflect the freshly updated discrete state.
+
+# Version 1.9.4.1
+* FIXED: Minor regression on GUI-only virtual `configuration`
+
+# Version 1.9.4 
+* INFO : Linux builds are made on Ubuntu 2024.04
+* ADDED: Change the way the threads are synchronized for container.
+* ADDED: force locale LC_NUMERIC="C" during container runtime to avoid (rare) issue during configuration. 
+* ADDED: GUI: `fmucontainer` builder now displays each FMU's icon (`model.png`) inside its node.
+* ADDED: GUI: the progress dialog shown during **Load**, **Import**, **Export**, and **Save**
+         operations now has a **Save Logs...** button to export the displayed execution logs
+         to a `.txt` file.
+* ADDED: GUI: `ts_multiplier` on a sub-container now materializes a GUI-only virtual `configuration`
+         node on the canvas, exposing one input port per checked sub-container
+         (`<container>.ts_multiplier`), wireable from any FMU. This node is purely a visual aid and
+         is never exported to the assembly (JSON/FMU). Unchecking `ts_multiplier` keeps the wire but
+         turns it (and the port) red until re-checked; the node is removed automatically once all
+         its ports are inactive and no wire (including red ones) references it anymore. Checking
+         `ts_multiplier` on the root container has no effect.
+* ADDED: GUI: a wire is now drawn in **red** on the canvas as soon as one of its port mappings is
+         invalid (broken port after "Replace FMU", or inactive `ts_multiplier` port on the
+         `configuration` node) — matching the red text already shown for invalid ports in the
+         *Wire Details* panel.
+* ADDED: `Assembly.write_json()`: FMU paths referenced in the `fmu`, `link`, `input`, `output`,
+         `start` and `drop` blocks are now made relative to the directory of the produced JSON
+         file, so exported assemblies stay portable (e.g. GUI **Export as JSON**). A new
+         `basenames_only` option references embedded FMUs by their bare filename instead
+         (used for the documentation copy embedded inside built FMU containers).
+* ADDED: GUI: new **Input Ports** tab in the FMU detail panel, symmetric to the existing
+         **Output Ports** tab. Each input port can be explicitly marked as *exposed*, causing
+         the generated assembly to declare it explicitly as a container input (via `add_input`)
+         instead of relying solely on `auto_input`. Exposed inputs on FMUs nested inside
+         sub-containers are automatically propagated up through parent containers.
+* FIXED: `fmusplit`: correct handling of FMI-3 array port connections (arrays are now properly
+         detected and linked in the generated assembly).
+* ADDED: GUI: when a wire is selected, a yellow direction indicator is drawn on the wire to
+         reflect the currently active tab of the *Wire Details* panel (A→B / B→A arrowhead at
+         the corresponding extremity, or a divergent ◀▶ marker at the middle for *Terminals*).
+* ADDED: `fmusplit`: detect terminal-to-terminal connections. Groups of port-to-port links whose
+         endpoints belong to two compatible terminals (same `terminalKind` / `matchingRule`) are
+         collapsed into a single terminal-level link in the produced JSON assembly. This lifts the
+         previous "LS-BUS clocks connection are not supported in GUI" limitation for FMU containers
+         where the peer FMU does not emit clocks (typical LS-BUS bus/node setups).
+* FIXED: `fmusplit`: correct parsing of clocked inputs/outputs in container.txt file format 4
+         (indexing bug that produced spurious cross-links between FMUs sharing a bus).
+* ADDED: GUI: on import, links between terminals declared in an assembly JSON are correctly
+         detected and routed to the wire's terminal mappings (visible in the `WireDetail` panel).
+* ADDED: `fmucontainer`: extended type conversions between all numeric types and booleans. 
+         Lossy conversions (narrowing, sign change, real↔integer, numeric→boolean) are applied with a warning.
+* ADDED: `fmucontainer`: support links between FMI-2 array-like ports (notation `name[k]`) and
+         FMI-3 array ports. FMI-2 element ports sharing a common `basename[]` are automatically
+         aggregated into a virtual array port named `basename` (dimension = number of elements),
+         which can be linked to an FMI-3 array port of the same dimension.
+         Multi-dimensional arrays are also supported using the Modelica-style comma notation
+         `name[i,j,...]` (conforming to FMI-2.0); elements are flattened in row-major order to
+         match the FMI-3 array layout.
+
+# Version 1.9.3.1
+* FIXED: `fmucontainer`: correct `fmi3SetString` for array variables (dimension > 1) and `fmi2GetBooleanStatus`
+* FIXED: `fmucontainer`: memory leaks and crashes under memory pressure; state machine improvements
+* FIXED: `fmucontainer`: `auto_parameter` works even if `auto_input` is not set. 
+* FIXED: `fmucontainer`: Clocks and Clocked variables management is made in Event Mode only
+* ADDED: GUI: Ability to replace a FMU in a Container
+* FIXED: `fmuplit` is able to parse conversion table
+* ADDED: FMI-3: support next event time
+* FIXED: GUI: Remove annoying Qt Runtime error message appearing during shutdown
+* ADDED: GUI: Terminals are supported in link definitions
+* ADDED: GUI: Contextual menu of FMUs to launch fmueditor, fmutool or FMPy (if installed)
+* ADDED: GUI: Highlight FMUs nested in the selected container
+* ADDED: GUI: Display tooltips for container parameters
+* ADDED: GUI: Easier link creation when FMU contains many variables (parameters displayed in italic)
+* ADDED: GUI: Import process now able to load SSP files
+* ADDED: GUI: Import/Export link definitions as CSV files (4-column format: FMU From, Port From, FMU To, Port To)
+* FIXED: FMU extraction of a container when using relative paths
+* FIXED: GUI: Import of containers with multiple levels of nesting (FMU inside FMU)
+
+# Version 1.9.3
+* ADDED: Graphical User Interfaces for quick FMU variable edition and build FMU Container
+* ADDED: Support of array variables
+* CHANGE: refactor the documentation
+* FIXED: `remoting` (rare) race condition when multiple instances share the same unzip directory
+* ADDED: `OperationSummary` display defined Terminals (if any)
+
+# Version 1.9.2.1
+* FIXED: `fmucontainer` embed the _original_ modelDescription.xml of the nested FMU instead.
+
+# Version 1.9.2
+* ADDED: `fmucontainer` support of Terminals
+* ADDED: support of Clock and Binary types
+* ADDED: `fmucontainer` support of Event-Mode
+* ADDED: `fmucontainer` support of LS-BUS. See [ls-bus.md](docs/user-guide/fmucontainer/ls-bus.md)
+* ADDED: `fmucontainer` support of `-datalog` option to log values at each step. See [datalog.md](docs/user-guide/fmucontainer/datalog.md)
+* ADDED: `datalog2pcap` command to convert datalog (csv file) into PCAP (binary file) to enable network analysis tools.
+         This tool is experimental.
+* FIXED: `fmucontainer` log correctly for FMU3 embedded inside FMU2 container
+* FIXED: `fmucontainer` correctly set start values
+* FIXED: `fmucontainer` correctly handle tolerance. See [issue 35](https://github.com/grouperenault/fmu_manipulation_toolbox/issues/35)
+* FIXED: `remoting` fix for very long path on windows 
+
+# Version 1.9.1.3
+* FIXED: `remoting` code should allow multiple FMUs to be instanciated (in less than 1 second).
+         There was a race condition in SHM name computation.
+         See [issue 38](https://github.com/grouperenault/fmu_manipulation_toolbox/issues/38)
+* FIXED: `fmucontainer` dynamic change of time_step: fix number of doStep() calls
+
+# Version 1.9.1.2
+* FIXED: Avoid usage of NULL pointer for category in logs. Despite this is legal, 
+         some FMI importers don't support it.
+
+# Version 1.9.1.1
+* FIXED: command line interface for `fmucontainer`, `fmutool and `fmusplit`
+
+# Version 1.9.1
+* FIXED: `fmucontainer` handle correctly start/stop in <DefaultExperiment>
+* ADDED: `fmucontainer` ability to dynamically change time_step. See [container-vr.md](docs/user-guide/fmucontainer/container-vr.md)
+
+# Version 1.9
+* CHANGE: `remoting` code rewrite to (drastically) improve performance
+* ADDED: `fmusplit` command to split container into FMU's and provide a json file
+* ADDED: `fmucontainer` support of `-sequential` mode
+* ADDED: FMI-3.0 early support. Use `-fmi 3` option for `fmucontainer`
+* FIXED: `fmucontainer` MT mode on Linux and Darwin
+* FIXED: `fmutool` command line for various operations
+* FIXED: `fmutool` handle correctly <ModelStructure>: remove empty tags
+* CHANGE: (API) `fmu_operations` and `fmu_container` packages are renamed `operations` and `container`
+* CHANGE: (API) Introduction of `FMUPort` and `port_attrs` method to replace `scalar_attrs` and `scalar_type`
+* CHANGE: (API) `FMUException` and `OperationException`  classes are renamed `FMUError` and `OperationError`
+* CHANGE: (CI/CT) Add some simulation steps
+
+# Version 1.8.4.2
+* FIXED: `fmucontainer` re-set start values for causality=input after fmi2EnterInitialization as workaround for some FMUs.
+
+# Version 1.8.4.1
+* FIXED: `fmucontainer` store embedded FMUs into shorter named directories to avoid windows-long-path-issue
+* FIXED: `fmucontainer` can refer to FMU located in subdirectory
+* FIXED: `fmucontainer` profiling reported incorrect values
+
+# Version 1.8.4
+* CHANGE: `fmucontainer` option `-dump` saves explicitly auto-wiring data. Auto-wiring is off for SSP format.
+
+# Version 1.8.3
+* FIXED: `fmucontainer` supports correctly auto-link for 1-to-n links
+
+# Version 1.8.2.2
+* ADDED: `fmucontainer` support fmi2Strings
+* FIXED: `fmucontainer` freeInstance correctly frees memory
+
+## Version 1.8.2.1
+* FIXED: `fmucontainer` exposed parameters name (using fmu name instead of fmu's model identifier)
+* FIXED: `fmucontainer` support for long path (on Windows)
+
+## Version 1.8.2
+* FIXED: `fmucontainer` identifier (for coSimulation) does not contain ".fmu" anymore
+* ADDED: `fmucontainer` log more information when embedded FMU cannot be loaded
+* ADDED: `fmucontainer` startTime and stopTime are deduced from the 1st embedded FMU
+* ADDED: `fmucontainer` support `-auto-local` option to expose local variables of the embedded FMU
+* ADDED: `fmucontainer` support new option `-auto-parameter` (parameters are not exposed by default)
+* FIXED: `fmutool` support "apply on" filter correctly
+* DEV: preliminary version of GUI for `fmucontainer`
+
+## Version 1.8.1
+* FIXED: `fmucontainer` read links from `.json` input files
+* CHANGE: switch to PyQT6 and add minor GUI improvements
+
+## Version 1.8
+* CHANGE: Python Package in now known as `fmu-manipulation-toolbox`
+* ADDED: `fmucontainer` support `canHandleVariableCommunicationStepSize`
+* ADDED: `fmucontainer` support `.ssp` or `.json` as input files
+* ADDED: `fmucontainer` new `-dump` option to save container description 
+
+## Version 1.7.4
+* ADDED: `fmucontainer` Linux support
+* ADDED: `-fmu-directory` option defaults to "." if not set
+* FIXED: `fmucontainer` ensures that FMUs are compliant with version 2.0 of FMU Standard
+* FIXED: `fmucontainer` handles the lack of DefaultExperiment section in modelDescription.xml
+
+
+## Version 1.7.3
+* ADDED: `fmucontainer` supports `-profile` option to expose RT ratio of embedded FMUs during simulation
+* ADDED: Ability to expose local variables of embedded FMUs at container level
+* FIXED: `fmucontainer` handles missing causality and handle better variability
+
+## Version 1.7.2
+* FIXED: handle `<ModelStructure>` section for `fmucontainer`
+* FIXED: brought back `-h` option to get help for `fmucontainer`
+* CHANGED: make compatibility with python >= 3.9
+
+## Version 1.7.1
+* FIXED: add missing *.xsd file that prevented checker to work
+* CHANGED: Checker use API instead of environment variable to declare custom checkers.
+
+## Version 1.7
+* ADDED: FMUContainer tool
+
+## Version 1.6.2
+* ADDED: Ability to add your own FMU Checker.
+* ADDED: SaveNamesToCSV will dump scalar types and start values.
+* CHANGED: Default (Generic) Checker checks the `modelDescription.xml` conformity against the XSD specification file.
+
+## Version 1.6.1
+* FIXED: publication workflow is fully automated.
+* FIXED: `fmutool` script is now part of the distribution.
+* CHANGED: minor enhancement in the README file
+
+## Version 1.6
+* First public release

fmu_manipulation_toolbox-0.0.dev3/CLAUDE.md

@@ -0,0 +1,3 @@
+- Use english language for documentation, comment and plan description.
+- plans should be stored in docs/local folder.
+- include the update of the user documentation at last step of plans.

fmu_manipulation_toolbox-0.0.dev3/CONTRIBUTING.md

@@ -0,0 +1,104 @@
+
+You’re welcome to share your ideas or join us in contributing to the project.
+By getting involved, you help enhance the project and make it accessible to a wider community.
+
+# How to Contribute 
+We value all types of contributions. Whether you discover bugs, improve the documentation, 
+or develop new features, there are many ways to get involved.
+
+## Reporting Issues
+
+If you encounter a bug or unexpected behavior, please follow these steps:
+
+1. Check the existing issues to see if the problem has already been reported.
+2. If not, open a new issue and include:
+  - A clear and concise description of the problem.
+  - Steps to reproduce the issue, if applicable.
+  - Details about your environment (e.g., operating system, Python version).
+  - Any relevant error messages or logs.
+
+## Suggestions for Improvements
+
+We’re always happy to hear new ideas for features or enhancements! If you’d like to suggest one:
+
+1. Check whether someone has already proposed it.
+2. If not, open a new issue describing the improvement and include:
+  - A clear explanation of the feature and its use cases.
+  - Why it would add value to the project.
+  - Examples of how the feature could work, if applicable.
+
+
+## Submitting Code
+
+For legal reasons, we are unable to accept pull requests. If you have ideas for improvements, 
+please create an issue or get in touch with the development team.
+
+## Running tests
+
+The test suite lives under `tests/` and uses [pytest](https://docs.pytest.org/). It is organised
+by test type:
+
+| Directory | Contents |
+|-----------|----------|
+| `tests/unit/` | fast, pure-Python tests (operations, checker) — no FMI simulation |
+| `tests/integration/` | container / split / CLI tests, file I/O, optional FMI simulation (`fmpy`) |
+| `tests/gui/` | PySide6 GUI tests (require `pytest-qt`) |
+| `tests/data/<area>/` | read-only reference data (FMUs, JSON, CSV, …) per functional area |
+
+### Install the test dependencies
+
+```bash
+pip install -e ".[test]"      # pytest, pytest-qt, pytest-cov, fmpy, numpy, PySide6
+# or, for a full dev setup:
+pip install -r requirements.txt
+```
+
+### Run the suite
+
+Tests are run from the `tests/` directory (the `pytest.ini` there sets the import paths):
+
+```bash
+cd tests
+pytest                        # run everything
+pytest --cov=fmu_manipulation_toolbox        # with coverage
+pytest -v integration/test_container.py      # a single module
+```
+
+### Selecting a subset with markers
+
+Markers are declared in `tests/pytest.ini`. Select (or exclude) with `-m`:
+
+```bash
+pytest -m unit                # fast unit tests only
+pytest -m "not gui"           # skip the GUI tests
+pytest -m "integration and fmi3"
+pytest -m lsbus               # LS-BUS tests
+```
+
+| Marker | Meaning |
+|--------|---------|
+| `unit` / `integration` / `gui` | test type |
+| `slow` | end-to-end test running an FMI simulation |
+| `needs_fmpy` | requires the `fmpy` package |
+| `needs_container` / `needs_remoting` | requires the compiled container / remoting binaries |
+| `windows_only` | only runs on win32 (auto-skipped elsewhere) |
+| `fmi2` / `fmi3` | exercises a specific FMI version |
+| `lsbus` | exercises the LS-BUS feature |
+| `area(name)` | selects the `tests/data/<name>` directory copied into `tests/tmp/<test>` |
+
+Platform- or binary-dependent tests are skipped automatically (with an explicit reason) when their
+prerequisites are missing — they never fail silently.
+
+### Adding a test
+
+1. Put reference data under `tests/data/<area>/` (inputs and `REF-*` files only — never commit
+   generated outputs).
+2. Add the test to the matching module in `tests/unit/`, `tests/integration/` or `tests/gui/`.
+3. Decorate it with the relevant markers, e.g. `@pytest.mark.area("<area>")`. The `area_dir`
+   fixture copies that data directory into `tests/tmp/<test>/` and `chdir`s into it, so your test
+   can refer to files by their bare names and write outputs without polluting the source tree.
+   The `tests/tmp/` tree is wiped at the start of every session and kept afterwards, so the
+   generated artefacts are easy to inspect when debugging a failure.
+4. Reuse the shared helpers in `tests/_helpers/` (`assertions.py`, `simulation.py`).
+
+

fmu_manipulation_toolbox-0.0.dev3/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2024-2026 Renault SAS
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+   notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+   notice, this list of conditions and the following disclaimer in the
+   documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.

fmu_manipulation_toolbox-0.0.dev3/MANIFEST.in

@@ -0,0 +1,15 @@
+# Content of the sdist (docs/local/packaging.md, decision D3).
+# With setuptools-scm, every file tracked by git goes into the sdist by default. Keep the Python package and the C
+# sources of the native binaries (container/, remoting/, fmi/); leave out the test data, the documentation, the CI
+# configuration and the prebuilt binaries.
+#
+# The wheel needs the prebuilt binaries: build it from the source tree, not from the sdist
+# (`python -m build --sdist --wheel`).
+prune tests/data
+prune docs
+prune .github
+recursive-exclude fmu_manipulation_toolbox/resources/win32 *
+recursive-exclude fmu_manipulation_toolbox/resources/win64 *
+recursive-exclude fmu_manipulation_toolbox/resources/linux32 *
+recursive-exclude fmu_manipulation_toolbox/resources/linux64 *
+recursive-exclude fmu_manipulation_toolbox/resources/darwin64 *