-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Needs a better name #41
Comments
I am thinking maybe
|
wasn't MLA just arbitrary to begin with? I see no reason to keep it in the name. I like:
|
ml is maximum likelihood so it is kind of descriptive. I don't think we should use ps because our stuffs is not necessary limited to point source analysis. Fit is also kind of arbitrary because likelihood maximization is not the only way to fit a physical model. I still prefer i3mla or skymla(and maybe adding pub). |
I mean, currently it is limited to point sources. how would that change? Also, if the 'a' is arbitrary, lets at least drop that |
Analysis. It can be extended to extended sources with a change in the preprocessor which can be added in the future. I don't think we need to limits ourselves to point source by adding it into the name of the package. Also having maximum likelihood in its kind of match the name of other package in 3ML like HAL(what HAWC use) |
MLA is pretty generic and gives my flashbacks to high school english class style guides. It's worth trying to think of a good name for the package before starting to talk about it more publicly, regardless of whether it conflicts slightly with submitted APS or ICRC abstracts.
Names can be purely descriptive (IceCubePointSourceFit) or more fun (Liz used to like the idea of Martin Wolf calling his code SkyWolf). Just something less generic. If there aren't ideas here, you could always have a poll in the #umd-backops channel on slack to get suggestions.
The text was updated successfully, but these errors were encountered: