ETC DEVELOPMENT SCHEDULE
========================

This schedule reflects the current ETC priorities.
We have not finished scoping the STIS work, so only ACS
and NICMOS are shown here.  The work needed to release
an APT NICMOS ETC equivalent to the CGI web ETC could be 
released in early July.  Adding the new NICMOS requirements 
will push the release to mid-August.

No one on the development team is full time, so the schedule is longer
than the estimated FTE levels.

- OCM INTEGRATION
  - ETC Integration       2/19/01 - 3/16/01   (Donald, Hemant)
  - Adding Mode Support   2/19/01 - 3/16/01   (Rob)

- ETC GUI Changes         4/1/01  - 4/25/01   (Donald, Hemant)

- ACS RAMP Filters   
  - Added to ETC          4/26/01 - 5/4/01    (Donald, Hemant)
  - Wavelength in OCM     Needed by 4/12/01   (Rob)

- ACS Coronograph 
  - GUI done under 
    ETC GUI Changes
  - Spatial Distrib work  Needed by 4/30/01   (Anand)
  - Integrating Spatial
    Distrib work          4/30/01 - 5/7/01    (Anand, Donald, Hemant) 

- Acceptance Testing      5/7/01 - 5/25/01    (Instrument Scientist, Leslie)
 
- Documentation           5/7/01 - 5/25/01    (Instrument Scientist, Leslie)

- June 1 Code Freeze      5/28/01

- June 1 External Release 6/1/01
  
- NICMOS Imaging
  - Current capabilities  5/7/01 - 6/8/01     (Anand, Donald, Hemant)
    Note completing this
    task make APT = CGI 
    WEB version
  - New capabilities      6/8/01 - 6/29/01    (Anand, Donald, Hemant)

- NICMOS Coronograph      6/29/01 - 7/13/01   (Anand, Donald, Hemant)

- NICMOS Spectroscopic    7/13/01 - 7/25/01   (Anand, Donald, Hemant)

- Acceptance Testing      7/25/01 - 8/8/01    (Instrument Scientist, Leslie)

- Documentation           7/25/01 - 8/8/01    (Instrument Scientist, Leslie)


OCM RELATED ISSUES
==================

These are issues related to get the OCM integrated
into the ETC and changes needed in the OCM to support
the ETC.

1) OCM integration will take 5 FTE level of effort
   with both Hemant and Donald working on it together.
   This translates to 6 weeks of calendar time, assuming
   both Hemant and Donald are working at .8 FTE level.

2) Chris to get science rule for ACS & NICMOS for inclusion
   into the OCM.  These are needed as soon as possible.
   STIS rules can come later.

3) Rob will have to add wavelength support and 
   mode support for the ACS.  These were estimated at
   3 days and 2 wks respectively.


ETC GUI CHANGES
===============

These are issues related to making GUI changes to support
the Phase 2 syntax and additional changes to the GUI needed
to support the ACS and NICMOS.  

1) GUI changes will take 3 FTE level of effort for 
   Donald and Hemant working together.  This translates
   to 3.5 weeks of calendar time, assuming .8 FTE level
   of support.

2) No Science support issues identified.  The development
   team has the GUI requirements.

RAMP FILTER SUPPORT
===================

These are issues for adding RAMP Filters to the ACS ETC.

1) This will take Donald and Hemant 1 week to add to the 
   ETC.  OCM changes are required for this effort

2) No additional Science Requirements identified.

ACS CORONOGRAPHIC SUPPORT
=========================

These are issues related to adding coronographic capabilities
to the ACS.  These issues were generated from the first draft
of requirements that Dick Shaw put together.  A later version
of these were written by John Krist.  These issues may need
to be updated based on John Krist's version.  This is just the
developer notes and FTE levels to implement the requirement.


Requirement 1
-------------

1) 1 day of development effort, no science input needed

Requirement 2
-------------

Simply explanation.  No effort involved.

Requirements 3, 6, 9, 10, 11
----------------------------

These 5 requirements were all related.  Some we combined
them into one task.

1) Anand will be doing the development work for the 
   calculation.  It was estimated that it will take Anand
   4 weeks to do this work

2) Anand, Hemant, and Donald need to work out the interface
   from the GUI input to the calculation code that Anand is
   developing.

3) Chris will work with John Krist to provide the input data
   for these requirements.

Requirement 4
-------------

1) The GUI development effort is included in the ETC GUI changes
   listed above.

2) In gathering the rules for the ACS, Chris will supply the rules
   and list of occulting spot options.

Requirement 5
-------------

1) The effort for this task in included in the ETC GUI changes
   listed above. 

2) We decided that the input would be in arcsec

Requirement 7
-------------

1) The effort for this task in included in the ETC GUI changes
   listed above. 

Requirement 8
-------------

1) The effort for this task in included in the ETC GUI changes
   listed above. 

2) There was a question about whether this should be supported for
   both the target and CS or just the target.  We decided that
   it should be supported for both.

Requirement 9
-------------

1) The development work was described above under requirement
   3.

2) There was a question about the need for a new S/N plot.  Here
   is the answer from the ACS group.  

   Chris,

   I'm not sure how important such a plot would be.  I think that
   just printing out a table that gives the s/n every arcsecond from
   1"-6", for instance, would suffice.  One can't take such numbers
   too literally since the observer is likely to subtract out the
   residual PSF anyway.

   John

Requirement 12
--------------

1) Anand to investigate the level of effort for this requirement.

Hi, all

I got this back from John Biretta...  I have not had time to digest it yet, 
but here is some email that contains necessary info for us if we are to
do 'the same as WFPC2' in the ACS ETC:

>  From biretta@stsci.edu Tue Mar 20 22:52 EST 2001
>  To: anands@stsci.edu
>  Subject: Re: wfpc2 erxposure time calculation  questions
>  
>  
>  Anand,
>  
>  The WFPC2 ETC assumes one is using PSF fitting rather than
>  aperture photometry.  This gives maximal signal-to-noise
>  since each pixel is weighted by its noise.  Historically,
>  new instruments like to show the largest possible signal-to-noise,
>  best possible detection limits, etc, hence this method was
>  used in early exposure calculations by the WFPC2
>  team at JPL, and we have tried to maintain consistency with
>  their estimates, since that is what users have come to expect.
>  
>  You can find some discussion of this at in the WFPC2 Handbook at 
>  
>  http://www.stsci.edu/instruments/wfpc2/Wfpc2_hand2/ch6_exposuretime6.html
>  
>  the parameter in question is called "sharpness" and in Tabulated in 
>  Table 6.5.
>  
>  In practive the WFPC2 ETC merely contains a copy of that table (6.5)
>  and does a simple lookup and interpolation based on the observation
>  wavelength, pixel size, and whether the PSF hits pixel center
>  or pixel corner.  It computes the SNR assuming all the counts fall
>  into one pixel, and then applies the correction to the SNR.
>  
>  Hope that helps, - John B.
>  
>  > 
>  > 
>  > Hi, John
>  > 
>  > I have a question about how the WFPC2 etc assesses its optimal aperture size
>  > (and what shape is used: circular aperture or rectangular/square box or other)
>  > for ETC calculations of signal to noise.
>  > 
>  > Would you be able to point me to the code doing this, and perhaps give
>  > me a quick walkthhrough the relevant bits if I need it?
>  > 
>  > The APT project's ETC's have been tasked to do the 'same as wfpc2' in this
>  > matter, so  I thought the WFPC2 ETC code would be a good starting point
>  > for me to see what is done there.
>  > 
>  > Regards,
>  > 
>  > Anand
>  > 
>  
   
NICMOS SUPPORT
==============

These are issues related to adding NICMOS capabilities to the 
APT ETC.  These requirements were provided by Santiago Arribas.
The requirements are on the APT ETC web page.  This is just the
developer notes and FTE levels to implement the requirement

Requirement 2.1
---------------

- It will take 3 weeks to support the current Web-Based CGI
  functionalities in the APT ETC.
  - 1 week to update the APT ETC GUI for NICMOS (Donald, Hemant)
  - 1 week to update the temperature calculations including
    reading in the reference files (Anand)
  - 1 week to update the communication interface between APT
    and synphot (Donald, Hemant)

Requirement 2.2 and 2.3 
-----------------------

- They are covered in detail in sections 4 and 5

Requirement 3 - Extending Imaging Capabilities
----------------------------------------------

Requirement 3.1.1 
-----------------

- This will take Donald & Hemant 1 day to update input data files

Requirement 3.1.2
-----------------

- This will take Donald & Hemant 3 days to complete.
  - 1 day for GUI changes
  - 2 days to copy/extend calculation in ACS model for NICMOS

Requirement 3.1.3
-----------------

- This will take Donald & Hemant 2 days to complete.
  - 1 day for GUI changes
  - 1 day to extend APT engine to use the new values

Requirement 3.1.4
-----------------

- It will take Donald and Hemant 1 day to update the GUI

- Chris needs to get some clarification on this issue about how
  to use these new values.  Does the software automatically figure
  out what value to use depending on the target location or does
  the user provide the value.  

- There is also a dependence on the Instrument Scientist team
  to supply the reference information.

Requirement 3.1.5
-----------------

- It will take Donald and Hemant 1 day to update the GUI

- Part of this is done already.  The APT ETC supports flux, lambda, and width.
  If we need the extended width, lambda and width capability we will need to
  either provide a way of inputing these values or convert from the flux, lambda,
  width inputs to extended width, lambda, width capability.  Chris was going
  to clarify what is really required.

Requirement 3.2.1
-----------------

- It will take Donald and Hemant 1 day to update the GUI

Requirement 3.2.2, 3.2.3
------------------------

- This work is updating the APT help files which should be done by an
  Instrument Scientist

- This is a dependence on the Instrument Scientist team

Requirement 3.2.4
-----------------

- Chris will need to get more requirements from the NICMOS team

Requirement 3.2.5, 3.2.6
------------------------

- This will be supported by the OCM.  No work needed.

Requirement 3.2.7
-----------------

- This work is updating the APT help files which should be done by an
  Instrument Scientist

- This is a dependence on the Instrument Scientist team

Requirement 3.2.8
-----------------

- This will be complete when 3.1.2 is implemented.  Once 3.1.2
  is done, this requirement will be met.  No additional work

Requirement 3.2.9
-----------------

- This work is updating the APT help files which should be done by an
  Instrument Scientist

- This is a dependence on the Instrument Scientist team

Requirement 3.2.10
------------------

- It will take Hemant and Donald 1 day to complete the 1st 
  part (non-difraction limited...)

- Chris will clarify parts 2 and 3.  Part 2 seems wrong and
  should be source = 0? Part 3 is confusing.

Requirement 4 - Coronographic
-----------------------------

- This work will be done by Anand under ACS req 10

Requirement 4.1.1
-----------------

- This will be done as part of the ACS coronograph work,
  No work needed.

Requirement 4.1.2
-----------------

- This will take Anand 1 day to implement

Requirement 4.1.3, 4.2.3
------------------------

- This will take Donald and Hemant 2 days to implement

- This will take Anand 2 days to implement the calculation changes

- Dependence on Instrument Team to supply Radial PSF

Requirement 4.1.4
-----------------

- This will take Hemant and Donald 1 day to implement

Requirement 4.1.5, 4.1.6, 4.1.7, 4.1.8
--------------------------------------

- All of this work will be done under the ACS coronagraph
  work Anand will do.  No additional work required.

Requirement 4.1.2
-----------------

- This will take Anand and Hemant 1 day to complete

Requirement 4.2.2
-----------------

- This will be supported by the OCM.  No additional work required

Requirement 4.2.4
-----------------

- This work is updating the APT help files which should be done by an
  Instrument Scientist

- This is a dependence on the Instrument Scientist team

Requirement 5 - Spectroscopic
-----------------------------

Requirement 5.1.1
-----------------

- No work required.  Available already.

Requirement 5.1.2
-----------------

- This will be supported by the OCM.  No additional work required.

Requirement 5.1.3
-----------------

- Same as 3.1.5.  No more work needed.

Requirement 5.1.4
-----------------

- No work needed.  Already available.

Requirement 5.2.1
-----------------

- This will take Hemant and Donald 1 day to complete

Requirement 5.2.2
-----------------

- This will take Hemant and Donald 1 day to complete

Requirement 5.2.3, 5.2.4
------------------------

- The OCM will support this.  No work needed.

Requirement 5.2.5
-----------------

- Already available, no effort.

Requirement 5.2.6
-----------------

- This work is updating the APT help files which should be done by an
  Instrument Scientist

- This is a dependence on the Instrument Scientist team


Requirement 5.2.7
-----------------

- Already available in APT ETC.

Requirement 5.2.8
-----------------

- This will take Hemant and Donald 1 day to implement

STIS SUPPORT
============

These are issues related to adding STIS capabilities to the 
APT ETC.  These requirements were provided by Kailash Sahu.
The requirements are on the APT ETC web page.  This is just the
developer notes and FTE levels to implement the requirement

TBD.

