Skip to content

Comments

Fix issue #2: t=0 -> t_i#408

Open
luciansmith wants to merge 3 commits intodevelopfrom
issue-2-ti-language
Open

Fix issue #2: t=0 -> t_i#408
luciansmith wants to merge 3 commits intodevelopfrom
issue-2-ti-language

Conversation

@luciansmith
Copy link
Member

Fix for new release of l3v2; new language for what 'initial time' means.

@fbergmann
Copy link
Member

@luciansmith I think it should be t_0 rather than t_i, since we explicitly want to mention the initial time.

@luciansmith
Copy link
Member Author

@fbergmann I'm not sure I understand. t_i is the initial time that we're explicitly talking about. In the current spec, we use 't_i' to talk about the earliest time that you have to calculate if there are delays, but in my revised version, I use t_i to mean the initial time, and just talk about 't < t_i' for the times before that. Will that work?

@dweindl
Copy link

dweindl commented May 12, 2025

Thanks for addressing this issue in SBML, @luciansmith ! I agree with @fbergmann that $t_0$ might be preferable. $t_i$ is correct, since it is defined as the start of the simulation time, but when just looking at any later section, $t_0$ might be clearer (or $t_{\mathrm{initial}}$, ...). When I see $t_i$, my first association would be that $i$ is some varying index, not "initial".

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