Skip to content

Fix logging levels and improve screen output via repr#247

Draft
spossann wants to merge 21 commits into
develfrom
225-logging-level-in-formatpy-is-incorrect
Draft

Fix logging levels and improve screen output via repr#247
spossann wants to merge 21 commits into
develfrom
225-logging-level-in-formatpy-is-incorrect

Conversation

@spossann
Copy link
Copy Markdown
Member

Solves the following issue(s):

Closes #225

@spossann spossann linked an issue May 22, 2026 that may be closed by this pull request
spossann added 9 commits May 22, 2026 14:55
… by excluding the non-pickleable runtime kernel wrapper from serialized state and rebuilding it deterministically.

What I changed

Added Domain serialization/copy hooks in base.py:
Internal rebuild path:
_build_args_domain
_can_build_args_domain
_rebuild_args_domain
Deep copy support:
deepcopy now deep-copies regular state, skips _args_domain, then rebuilds _args_domain.
Pickle support:
getstate removes _args_domain from state.
setstate restores state then rebuilds _args_domain.
Defensive runtime access:
args_domain property now lazily rebuilds if missing/None and raises a clear error if state is incomplete.

Added regression tests in test_domain.py:

test_domain_deepcopy for Cuboid and IGAPolarCylinder.
test_domain_pickle_roundtrip for Cuboid and IGAPolarCylinder.
Both tests verify:
reconstructed DomainArguments exists and is separate object
numerical evaluation consistency after deepcopy/pickle round-trip
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Logging level in format.py is incorrect

1 participant