Escolar Documentos
Profissional Documentos
Cultura Documentos
Data Import
Format
Either widely used/accepted, or Can be converted easily from something widely used User need not know the details of the format Well documented (e.g., which flavor of latitude).
Disk I/O speeds do not follow Moores law Read speed is more important than write speed Caching File size is only important to keep access times low
Fast Access
Content must represent the details of the data E2E - Full intent of the observer must be embedded
Data Export
Format
Either widely used/accepted, or Can be converted easily into something widely used User need not know the details of the format Well documented (e.g., which flavor of latitude).
Fast Access
Disk I/O speeds do not follow Moores law Read speed is more important than write speed
Content must represent the details of the data E2E - Full intent of the observer must be embedded.
Various levels of granularity Calibrated and raw data E2E - User can add annotation/comments Security Only the observer can access data
Data Archive
Write speed more important than read speed. File size is very important Cannot anticipate types of user queries
Large number of columns in data base index Very sophisticated/fast RDBMS
User should be able to see the data within an integration of when it was taken (or N seconds).
User Interface
Command line
Familiar syntax better than a good syntax Procedural with byte-wise compiling (performance) History, min-match or command completion Useful error messages Interruptible Error trapping and exception handling Ability to Undo
User Interface
GUIs best for:
Interacting with data visualizations Filling in forms
data base queries options for data pipelines
Browsing for data files Defining E2E data flow (ala labview)
Imaging Tools
Visualization
Shouldnt try to recreate those things already available in another package export instead.
Analysis Algorithms
Algorithms well documented Study what exists in other packages. Robustness very important but so is speed
Provide less robust but faster alternatives
Developers should not force an algorithm on users Developers should provide defaults only Building blocks better than a do-all algorithm. Ability to use and modify header information as well as data. E2E do-alls are built out of the same building blocks.
Documentation
On-line and hardcopy
Tutorials/Quick Guides Cookbook
Based on observing types
Reference Manuals
Full, gory details Data Formats Algorithms
Searchable by keywords
Quick, interactive command help from within the system. Never release until these are in place
User Support/Feedback
A familiar system minimizes staff support Easily accessed, on-line help desk and Suggestion box Automatic generation of bug reports Observers of observers
Marketing
A familiar system already has a market Dont be another cereal on the supermarket shelf Workshops are better than papers Create a User Community Responsive feedback from developers Independent Beta testers Reputation & first experiences are everything
User Community
User Forums Newsletters Accept User Contributions/Additions
Sourceforge-like system NRAO-seal-of-approval
NRAO Moderator
Display happens within an integration of when data were taken tied to real time filler GUI based underlying language is unimportant Output understandable by an operator
Analysis happens within an integration of when data were taken GUI based underlying language is unimportant Output understandable by an operator
Default algorithms for all observing cases Extensible as new algorithms are developed User-defined/tweaked algorithms Robust and not-so-robust algorithms