Документ взят из кэша поисковой машины. Адрес оригинального документа : http://xmm.vilspa.esa.es/external/xmm_sw_cal/icwg/presentations/FD_CM.txt Дата изменения: Tue Jun 20 16:46:27 2006 Дата индексирования: Sat Dec 22 14:42:47 2007 Кодировка: Поисковые слова: hst

Form Discussion: Cal Management:

Came up with goals and role of ICWG. Web page with definition of what CAL is - e.g. "Ability to use poisson stats
in data". Will discourage publication of wrong results. Standard Cal database set-up needed. Pre-flight qual assurance
to include ground calibration.

Web pages to be hosted at a neutral site. Idea of a calibration PI from instrument teams. Leo - agency should
maintain responsibility for this function. MK - in practise cal done by instrument teams, CAL PI is not in PI team
but works outside of it. Chandra have this already contracted out to Smithsonian. Question - how much authority
would this role have ? Leo - should be enough to get cal obs pushed through.
SFS - can we highlight problems and make recommendations to missions ?
RM - science issues are the way to push it. "We can't resolve this problem unless the cal is improved to X%".

S-Z effect led Chandra cal effort for a while although turned out to be more diff than expected.

Management - need to preserve GC data in standard format. Ok for big missions, but can the smaller missions
be encouraged to do this ?

Where are the data from european missions stored ? ESA missions at ESAC, others at Leicester.
Does Europe need another version of HEASARC ?

Science working groups dont necessarily understand enough about instrumentation and CAL to set priorities
correctly. CAL PI needs to be intimately involved with instrument team to be useful. The quality assurance issue
is important - this way we can make the calibration more important during development and not get it squeezed at the
end, just before launch. Must go into the initial development plan. Dont think of calibration as your "schedule contingency".