Changes between Version 20 and Version 21 of pstamp_web_interface_features

Timestamp:

Jan 13, 2010, 12:23:00 PM (16 years ago)

Author:

welling

Comment:

--

pstamp_web_interface_features

@@ -187 +187 @@
 === Presentation of Results ===
 
-When a request completes, the results file should be parsed and importand data presented
+When a request completes, the results file should be parsed and important data presented
 to the user in an easy to understand way.
 
@@ -230 +230 @@
 === Patterns of Use ===
 
-Presumably the most common usage pattern will be to collect observations of a transient.  This interface works reasonably 
-well for this.  We've included a feature to generate a table of grayscale images within an html index.  This turns out
+Presumably the most common usage pattern will be to collect observations of a transient.  We've included a feature to 
+generate a table of grayscale images within an html index.  This turns out
 to be a nice way to select 'useful' images.  These can be selected and more detailed information (image, weight and mask) 
 can be downloaded.  The trick is to avoid images for which the source of interest is hidden by a mask.
 
 === Comparison to IPP Stampserver Functionality ===
+
+For this system the source images are precomputed and available, whereas they must be computed on demand in the IPP framework.  
+On the other hand, the source data for *all* observations is available to the IPP framework.  Would it be possible to display 
+observations for which computation was necessary in gray?  The user could then select them and click a button to cause them
+to be processed; the display would update to show them no longer gray when the processing was complete.
+
+It would be hugely helpful to have the masks immediately available.  The user could then select images for further processing 
+based on the masks, avoiding the computation of unnecessary images.
+
+User accounts can easily be added via the usual Apache mechanism.
 
 === Underlying Software ===