Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes #2761 change transport direction #2818

Conversation

msevestre
Copy link
Member

@msevestre msevestre commented Oct 23, 2023

Fixes #2761

Description

Probem was that it was seen as a non structural change (e.g. changing the expression profile structure). now I am also checking that all used expression profile have the same structure version

Type of change

Please mark relevant options with an x in the brackets.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires documentation changes (link at least one documentation issue):
  • Algorithm update - updates algorithm documentation/questions/answers etc.
  • Other (please describe):

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Integration tests
  • Unit tests
  • Manual tests
  • No tests required

Reviewer checklist

Mark everything that needs to be checked before merging the PR.

  • Check if the code is well documented
  • Check if the behavior is what is expected
  • Check if the code is well tested
  • Check if the code is readable and well formatted
  • Additional checks (document below if any)
  • Check if documentation update issue(s) are created if the option This change requires a documentation update above is selected

Screenshots (if appropriate):

Questions (if appropriate):

@msevestre msevestre requested a review from Yuri05 October 23, 2023 19:19
if (!sameStructureVersion)
return false;

//For individual, there is a special handling required as we need to also check that the used expression profile have hte same structure version
Copy link
Member

Choose a reason for hiding this comment

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

typo: "hte" => the

if (!sameStructureVersion)
return false;

//For individual, there is a special handling required as we need to also check that the used expression profile have hte same structure version
Copy link
Member

Choose a reason for hiding this comment

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

Do we need a special handling for populations as well?

Copy link
Member Author

Choose a reason for hiding this comment

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

nope. We dont allow commit or update for population

Copy link
Member

Choose a reason for hiding this comment

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

ok

Comment on lines 160 to 163
//let's compare the expression profile in each individuals and see if they are comparable
//not the same length of expression profile, structural change
if (usedIndividual.AllExpressionProfiles().Count != individualTemplate.AllExpressionProfiles().Count)
return false;
Copy link
Member

@Yuri05 Yuri05 Oct 24, 2023

Choose a reason for hiding this comment

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

Is it actually possible, that sameStructureVersion in the code above is true, but we have a different number of expression profiles??

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think so. you are right this check can be removed.

@Yuri05
Copy link
Member

Yuri05 commented Oct 24, 2023

If we use a PR template, we should also tick some options when creating a PR 😉

@msevestre
Copy link
Member Author

Agreed. I forgot to check. Still have to get used to doing this here

@msevestre msevestre merged commit c6157b3 into develop Oct 24, 2023
@msevestre msevestre deleted the 2761-changing-transpor-direction-in-the-expression-is-not-applied-in-the-simulation branch October 24, 2023 15:44
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.

Changing transpor direction in the expression is not applied in the simulation
2 participants