Skip to content

Conversation

@daklauss
Copy link
Collaborator

@daklauss daklauss commented Jun 6, 2025

Added the Cases i used for the fractionating topic as test to have a small suit that checks wheter the standard fractionoptimizer and it's default parameter are suitable. Hopefully this shows possible instabilities with the cobyla optimizer when changing parameters.

I guess the cobyla fixture is a litle bit messy.

Also changed the parameters for tol and rhoberg another time.

@schmoelder schmoelder changed the title Test fractionating Test fractionation Jun 6, 2025
@schmoelder schmoelder changed the title Test fractionation Add tests for fractionation module Jun 6, 2025
@schmoelder schmoelder force-pushed the test_fractionating branch from 2aef263 to e9ac63a Compare June 12, 2025 09:28
"""Class to create a faked SolutionIO object with a Gauss function."""

def __init__(self, solution_struct, comp_system):
"""solution struct has to be a dictionary with
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Improve docstring

)


class GaussianPulse(SolutionIO):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't it make sense to update the solution fixtures in test_solution.py?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider a different name. "Fractionating" is not a really a thing. Consider what exactly you are testing here. Is it the FractionationOptimizer? Is it performance?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this make the optimization more robust or is this just "to play around"?

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.

3 participants