Git Product home page Git Product logo

Comments (5)

drbergman avatar drbergman commented on August 16, 2024

If you flip the ordering of the cell definitions within the xml, then the reverse happens: all cells undergo random time to finish apoptosis.

from physicell.

rheiland avatar rheiland commented on August 16, 2024

The .xml config file you provided is malformed and will cause PhysiCell to output warnings which may confuse the debugging process. It has nothing to do with the actual issue though. Specifically, the .xml specifies a non-existent "default" cell type in various blocks, e.g., <cell_interactions>. I think the attached .xml is correct. Still looking at the issue...
fixed.zip

from physicell.

drbergman avatar drbergman commented on August 16, 2024

from physicell.

rheiland avatar rheiland commented on August 16, 2024

Spent several hours looking into this. Just want to make some brief comments here for now. May need to get Paul's input for a well thought out solution, but welcome input from others. This issue involves both the apoptosis and necrosis death models. And so far, I've only tested the case where <phase_durations> are provided for those models (not phase_transition_rates). When there is more than one cell_definition defined, each one will have its apoptosis and necrosis:

  • fixed_duration attribute (boolean) value to be that of the last cell_definition
  • <duration> value to be that of the last cell_definition

The reason for this is due to fact that, for each pointer pCD to a new cell_definition, pCD->phenotype.death.models[death_index] points to the same address. Similarly for the reference address &(pCD->phenotype.death.models[death_index]->phase_links[start][0].fixed_duration). Therefore, as we parse the .xml and generate values in data structures for the apoptosis and necrosis death models, these values are overwritten with each new cell_definition.

from physicell.

MathCancer avatar MathCancer commented on August 16, 2024

we shoudl migrate teh "fixed duration" booleans from the graph strucure to the param strucxture fore each cycle model.

from physicell.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.