Closed dncnwtts closed 2 years ago
This seems good to me, although I'm not sure I understand the indexing scheme, where, for example, TOD_INIT
and NUM_GLOBAL
is the same.
Otherwise I think this looks nice.
Yes, the numerical values are the same, but the actual timer index for the channel-specific cases is
index = NUM_GLOBAL + (band-1)*NUM_TOD + {requested timer}
So the per-channel indices are relative to a fixed offset per channel.
Den 19.11.2021 13:30, skrev Duncan Watts: This seems good to me, although I'm not sure I understand the indexing scheme, where, for example, |TOD_INIT| and |NUM_GLOBAL| is the same.
Otherwise I think this looks nice.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Cosmoglobe/Commander/issues/115#issuecomment-974031943,
or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUFTO5LL2CE3T5VX27VS4DUMY7PJANCNFSM5IMASOWA. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
Still missing from this module:
Here's a proposal for a Commander timing module. Any comments or suggestions? The idea is essentially to introduce a lot of timers in a new class, and one can start and stop each of them individually (like this:
call timer%start(TOT_RUNTIME)
), and ask for an ASCII report to be dumped to a given file. There are two types of timers, namely global and per-channel.