Hi all (whereby 'all' I'm particularly looking at @evan012345 and @moukaddam) - recent events have emphasized how badly this package needs a test suite that we can use to check if things have broken since the latest commit; I'm hoping to find someone with some bandwidth for this in the near future, but a quick and dirty interim substitute would be a collection of .mac files that run the various parts of the simulation; it's a pretty sorry substitute for a real test suite, but at least then we could check and make sure they all still run at every new revision. No need to write anything new for this - we can just throw a selection of what you're already using into a new /macros folder, at least until a real test suite gets built.
Hi all (whereby 'all' I'm particularly looking at @evan012345 and @moukaddam) - recent events have emphasized how badly this package needs a test suite that we can use to check if things have broken since the latest commit; I'm hoping to find someone with some bandwidth for this in the near future, but a quick and dirty interim substitute would be a collection of .mac files that run the various parts of the simulation; it's a pretty sorry substitute for a real test suite, but at least then we could check and make sure they all still run at every new revision. No need to write anything new for this - we can just throw a selection of what you're already using into a new /macros folder, at least until a real test suite gets built.