Skip to content
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

Open
mjlarson opened this issue Feb 16, 2021 · 5 comments
Open

Needs a better name #41

mjlarson opened this issue Feb 16, 2021 · 5 comments

Comments

@mjlarson
Copy link
Collaborator

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.

@jasonfan1997
Copy link
Member

jasonfan1997 commented Feb 17, 2021

I am thinking maybe

  1. i3mla
  2. icecubemla
  3. skymla
    For the first two it is pretty straight-forward. skymlais also an option because all the other IceCube packages start with Sky(except csky). I am also open to other ideas.

@thejevans
Copy link
Collaborator

wasn't MLA just arbitrary to begin with? I see no reason to keep it in the name.

I like:

  • icepub
  • icefit
  • i3-pspub
  • i3-psfit
  • i3-pubfit

@jasonfan1997
Copy link
Member

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).

@thejevans
Copy link
Collaborator

thejevans commented Feb 18, 2021

I mean, currently it is limited to point sources. how would that change?

Also, if the 'a' is arbitrary, lets at least drop that

@jasonfan1997
Copy link
Member

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants