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
In designing Korg's top-level API, I'm taken some care to break things apart where appropriate. For example, I think it's fundamentally correct that interpolate_marcs, format_A_X, apply_LSF etc, are separate functions.
However, as things get more complex, I'm taking more seriously the idea of having a simple top level function (Korg.spectrum?) that requires even less documentation-reading (initial credit to Alex Ji for this idea, I think).
Ideally, this would have no positional arguments except wavelength specifiers, that means that there would have to be a default linelist. This is the biggest hurdle, and may be the thing that prevents me from doing it.
Any ideas about how to simplify Korg's interface for the median use case are welcome.
The text was updated successfully, but these errors were encountered:
In designing Korg's top-level API, I'm taken some care to break things apart where appropriate. For example, I think it's fundamentally correct that
interpolate_marcs
,format_A_X
,apply_LSF
etc, are separate functions.However, as things get more complex, I'm taking more seriously the idea of having a simple top level function (
Korg.spectrum
?) that requires even less documentation-reading (initial credit to Alex Ji for this idea, I think).Ideally, this would have no positional arguments except wavelength specifiers, that means that there would have to be a default linelist. This is the biggest hurdle, and may be the thing that prevents me from doing it.
Any ideas about how to simplify Korg's interface for the median use case are welcome.
The text was updated successfully, but these errors were encountered: