Difference: StatusAndImprovements (1 vs. 2)

Revision 22017-01-12 - KarlVyhmeister

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
  • TODO
Changed:
<
<
  • Database
>
>
 
    • Deploy the current design of DB on pharos.
    • API to connect to the DB: from the requests page, from the marshal, connection to the modon DB, etc.
    • Connect the pipelines with the DB to log the reductions.

Revision 12016-10-17 - NadiaBlagorodnova

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="WebHome"
  • TODO

  • Database
    • Deploy the current design of DB on pharos.
    • API to connect to the DB: from the requests page, from the marshal, connection to the modon DB, etc.
    • Connect the pipelines with the DB to log the reductions.
    • Send an email once everything has been reduced. If at 9:00AM something is NOT reduced, send an email to the developers.

  • Web site
    • Find out what machine shall host the web site. Best bet is yupana. What restrictions apply? User/password or open to all?
    • How the file access is going to be managed? By project? Access by FTP to only the project files.
    • Implement the front end that is connecting to the DB. It needs to show: images taken the night before, statistics on FWHM, temperature, etc.
    • Implement the access of reduced files through the website (connection to IPAC??? directly from pharos???).
    • Show images of each image taken to assess the quality,

  • Observation planning
    • Version of the robot to account for: periodic observations (Eric's request for variable stars), split time between the projects, account for weighting the time according to bright/grey/time request.
    • Include all this into account fro the scheduler.

  • IFU pipeline
    • Better background removal for each trace: improve speed, improve S/N.
    • Investigate the background extraction (using PCA?) to eliminate A/B pair and use A only.
    • Automatic extraction of sources, i.e. create a fits file with the summed flux of each spaxel and extract all the apertures in the image.
    • Test the performance of the S/N on the extracted spectrum with each focus step.
    • Create an SEDM fits file writer, so that it includes: extracted spectrum, sky background, noise spectrum, etc.

  • Automatisation
    • Make snid to run automatically and grab the optimum template. Store the best template in the txt/fits file header.
    • Include the initial classification int he PTF report.

-- NadiaBlagorodnova - 17 Oct 2016

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback