WISE archive STATS page =================================== 1). A separate figure to show the skycoverage for OPS coadd data. This has been urgently requested by the science team. ----- Mi Wei is the only person working on this web page, she can work on this in next a few days. Delivery date is next Friday: April 30th. 2). In addition, Roc suggested to collectively show with a figure the scan IDs in the archive. ------ This is done, GATOR has the capability, using inventory data tables. 3). For a given position, is there a way to show if the data at this position is in the archive? ---- 1). GATOR has a way, 2). Image archive can do it. 3). can we have the STAT page do this? ---- yes, write a help-page, link this page to the STAT page, as well as improving the image archive no-data found page. ---- draft by next monday, will give an estimate of delivery date. GATOR ============================== 1). Is it possible to create a link to return 'Back to Search Page' or 'Modify Search' link to the results page that sends the user back to the page where the search parameters are input. Right now I use the back buttons, but if I don't go back fast enough, it resubmits the search and spawns a new query. ---- not immediately since this affects many database. We need time to carefully test it. Steve will discuss with Angela to decide the time scale. Image Archive ============================= 0). Bug in the table upload: Davy wrote: "I've uncovered a couple of problems with the latest version of the WISE Image Service on ceres when used in table upload mode (see first screen grab for the parameters I set): -- When I ask for cutouts at different positions from the same coadd, the same cutout image is repeated for all sources on that coadd (see second and third screen grabs). " This has been confirmed by Steve as a bug and will be fixed. The exact date is in discussion. ------- Delivery date: Serge will work on this next monday, April 26, expect to complete by April 27th. 1). Bug in the table upload image output: Davy wrote: "Even though I ask only for bands W1, W2, and W3 (in order to make a 3-color image based only on those three bands), I'm served all four bands and the default 3-color image uses W2+W3+W4. I don't see any way to change this to what I need." "I still contend that this is a bug. If I use the Image Service in single object mode and ask only for W1, W2, and W3, it gives me back just those three bands and builds a 3-color jpeg based only on those three. If I ask for the same thing in table upload mode, it lists only W1, W2, and W3 in the table but serves me back all four bands, thereby ignoring my request. It defaults to making 3-color jpegs on the three longest wavelength bands which is not what I wanted." ------- Need to discuss with Serge on the detail and date of delivery. 2).Bug fix: batch download script: Cushing has found some errors and his message has been forwarded to Groom. ---- Steve will figure out the delivery date, this item for discussion next week. 3). a stamp image (jpeg format) cutout tool for wise data a large number of sources for table upload query. At this point, no need to create new image display page for the current version. Maybe later release we can create a better presentation form. ---- Steve will talk to the IRSA team, meet next week to decide on the delivery date. Science team requirement time frame is within 1 month from today, April 23, 2010. 4). image display scaling: Is it possible to skip 999 pixel values for non-image when auto-scale the image display? This will produce better stretches, so avoid frequent user adjustment. ---- desirable to have as soon as possible, but not urgently needed. 5). Marking artifacts on level 1b images. This item has been identified earlier, and needs to be implemented soon. --- this is critical: need to decide on the delivery date (next friday discussion item) 6). Visualization of level 1b images for a single or multiple sources: This item has been discussed at the early stage design of the image archive. We need to revisit this issue again. The current form is very difficult to use and offers very little useful information for the science users. Can we have a meeting with more relavent people to discuss this specifically? ----- This is critical for the public release. Extremely useful for the science team before the public release. Decide on the delivery date in next discussion.