You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tau version: 0.7 (v0.7-alpha-162-gc534f60)
Build: c534f60
OS: Ubuntu
** Summary **
I was trying to use a two time-line recurrence relations, but there is a major inconvenience when the recurrence is evaluating the edge timeline between its base case and general case. Even though a proper base case is declared before the general case, the relation still tries to use its general case going into negative timeline index, I believe, and throwing out (Warning) shift creation: left < right. It manages to skip that part with just a warning, so there is no crashing or hanging, but due to the multi-timeline nature of this example the problem keeps on accumulating further down the recurrence spamming the output with lots and lots of warnings.
** Notes **
In this situation I would be expecting the base case to take priority over the general case, thus eliminating any potential errors or warnings due to evaluation of the latter. I also tried to work around it by supplying all 4 of r[0,0] r[0,1] r[1,0] r[1,1] initial values in the defs, but it only delayed the problem into the subsequent step.
Contact details: Telegram @ksdjfskfh
The text was updated successfully, but these errors were encountered:
Tau version: 0.7 (v0.7-alpha-162-gc534f60)
Build: c534f60
OS: Ubuntu
** Summary **
I was trying to use a two time-line recurrence relations, but there is a major inconvenience when the recurrence is evaluating the edge timeline between its base case and general case. Even though a proper base case is declared before the general case, the relation still tries to use its general case going into negative timeline index, I believe, and throwing out (Warning) shift creation: left < right. It manages to skip that part with just a warning, so there is no crashing or hanging, but due to the multi-timeline nature of this example the problem keeps on accumulating further down the recurrence spamming the output with lots and lots of warnings.
** Input **
** Screenshot **
** Notes **
In this situation I would be expecting the base case to take priority over the general case, thus eliminating any potential errors or warnings due to evaluation of the latter. I also tried to work around it by supplying all 4 of
r[0,0] r[0,1] r[1,0] r[1,1]
initial values in the defs, but it only delayed the problem into the subsequent step.Contact details: Telegram @ksdjfskfh
The text was updated successfully, but these errors were encountered: