9 | | We should investigate why {{{resolveLoops}}} does not figure this out, and extend that algorithm to also handle this case. Then, we should also consider whether to make {{{resolveLoops}}} active by default, as it may be essential in handling some models which are found out there. Unfortunately we can't think of trying it after index reduction has failed, because the failure is not structural (which could be caught by the backend), but rather numerical, and so only visible at runtime, se we'd need to make sure that resolveLoops always works fine. |
| 9 | We should investigate why {{{resolveLoops}}} does not figure this out, and extend that algorithm to also handle this case. Then, we should also consider whether to make {{{resolveLoops}}} active by default, as it may be essential in handling some models which are found out there. |
| 10 | |
| 11 | Unfortunately we can't think of trying it after index reduction has failed, because the failure is not structural (which could be caught by the backend), but rather numerical, and so only visible at runtime, se we'd need to make sure that {{{resolveLoops}}} always works fine. |