This page has been inactive since August 2005 and should be considered of historical interest only. A more recent page with tool-naming issues is Proposed Tool Name Changes 29 May 2007

Proposed tool names

Names for the tools that follow the "gt" prefix convention have been proposed in the Science Tools Working Group meeting. Here is a copy of the table that was presented during the meeting with a column added for the package owners to enter their preferred names (when they differ):

Current name

Proposed Name

Preferred Name

TsMap

gttsmap

 

count_map

gtcntmap*

 

dataSubselector

gtdatasubsel

gtselect

diffuseResponses

gtlikediffresp

gtdiffresp

evtbin

gtcntmap*

gtbin

expMap

gtexpmap**

 

exposureMap

<may go away>

 

exposure_cube

gtlivetimecube

 

exposure_map

<merge with gtexpmap?>**

 

glbary

gtbary

 

gtbindef

gtbindef

 

gtcntsmap

<merge with gtcntmap?>*

 

gtsrcmaps

gtsrcmaps

 

likelihood

gtlikelihood?

gtlike

makeExposureCube

<merge with gtlivetimecube>

gtlivetime

obsSim

gtobssim

 

orbSim

gtorbsim

 

pulsePhase

gtpulsephase

gtpphase

rspgen

gtrspgen

 

sourceIdentify

gtsrcid

 

stpsearch

gtpsearch

 
  • No labels

6 Comments

  1. James Chiang

    • gtselect follows in the naming tradition of FTOOLS fselect and xselect that perform similar tasks.
    • evtbin presently does more than just create counts maps, so gtcntmap probably isn't the best name.
    • exposure_map and expMap should not be merged.

  2. Seth Digel

    James Peachey proposed that 'evtbin' become 'gtbin' for the reason given above. Also, he proposed that 'gtlivetimecube' be shortened to just 'gtlivetime'.

  3. Seth Digel

    James also pointed out that we'd still be good citizens in the FTOOLS world if we wanted to add a hyphen after the gt for readability, e.g., gt-like, gt-srcmaps, gt-rspgen, gt-obssim. It helps a little, I think, and may make just ignoring 'gt' easier when pronouncing the names.

  4. Unknown User (hirayama)

    It looks like gtsrcmaps is the only name that has "s" at the end.
    Is there any reason for that?

  5. James Chiang

    Yes, it creates more than one map if there is more than one source in the model, as there is wont to be. If it is preferable, "gtsrcsmap" is ok by me.

  6. Jean Ballet

    I don't like the idea of adding a hyphen in all the names. Just a useless character to type in my opinion, and a convention not used by anybody else.
    To avoid misunderstandings in the general comunity, I think gtexpmap should be the tool that builds what is usually called an exposure map in other contexts, ie currently exposure_map and exposureMap. We should find some other name for expMap (gtlikemap ?).
    I don't like gtlivetime for exposure_cube. I would prefer the word cube in the name. Why not simply gtexpcube ?
    Finally, I find gtlike a little elliptic for likelihood. gtlikelihood is OK with me. Another (shorter) possibility would be gtsrcfit.