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

"Extend" of Initial conditions: Introduce container criteria for molecules #2355

Open
Tracked by #2130
rwmcintosh opened this issue Oct 30, 2024 · 1 comment
Open
Tracked by #2130

Comments

@rwmcintosh
Copy link
Member

No description provided.

@rwmcintosh rwmcintosh added this to v12 Oct 30, 2024
@PavelBal PavelBal self-assigned this Nov 4, 2024
@PavelBal
Copy link
Member

PavelBal commented Nov 5, 2024

Okay, so what we need is some kind of Container criteria for molecules that are respected when extending the IC BB.

  • \<Molecule>-FcRn_Complex are present in Plasma, Interstitial, Endosome and "Not in container: BloodOrgan"
  • FcRn only in Plasma, Interstitial, Endosome and "In Container: EndogenousIgG"
  • LigandEndo only "In container: EndogenousIgG"
  • LigandEndo_Complex only in Plasma, Interstitial, Endosome and "In Container: EndogenousIgG"

This would also solve #2356

@PavelBal PavelBal removed their assignment Nov 5, 2024
@PavelBal PavelBal added this to the OSMOSES vNext milestone Nov 6, 2024
@PavelBal PavelBal removed this from v12 Nov 6, 2024
@PavelBal PavelBal changed the title "Extend" of Initial conditions: by default, do not extend for FcRn-complexes (e.g. "Fluvoxamine-FcRn_Complex") (== use PK-Sim knowledge). This should be managed by a check box (e.g. "Do not create for FcRn blabla..") "Extend" of Initial conditions: Introduce container criteria for molecules Nov 22, 2024
@github-project-automation github-project-automation bot moved this to Under discussion (technically feasible; open for sponsorship) in OSP Suite Software Roadmap Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Under discussion (technically feasible; open for sponsorship)
Development

No branches or pull requests

3 participants