Beta 1
Target: basically usable for everything we want to support in the first release. Should replicate all features of Finesse 2.0.
Some specific focuses:
-
Investigate how people are performing simulations with the alpha releases and figure out what tools they are missing and add them here. For instance, how are people performing complex simulations that involve adding and removing detectors, changing values, etc.? Is it the old "Pykat" style of deep copying models, or more of an "action tree" style with the new analysis syntax? See this chat conversation for more info.
-
Think whether there is any special KatScript syntax needed to support non-modal simulations like LCT/FFT/time domain. Is KatScript to be mainly for modal simulations only? Should we push people towards the Python API when they want to do other sim types? Or should we try to make LCT/FFT/time domain sims first class citizens in KatScript as well? If so, do we need to have "action" style syntax for other simulation types too or does that not make sense? Would we want to be able to mix simulations, e.g. "lock" a model with modal and then perform FFT? Do we need a special "switch" command (or parameter to actions) that tells Finesse which simulation type to apply (can be modal by default)?