SDM Binary Data Format:



Similar documents
A brief introduction to the Measurement Set and the ALMA Science Data Model

Electronic Mail

DOCO EasyScan Solution for the London Insurance Market

Lesson 4 Web Service Interface Definition (Part I)

Developing Java Web Services

AS2 AND EDI OVER THE INTERNET FAQ

Appendix M INFORMATION TECHNOLOGY (IT) YOUTH APPRENTICESHIP

IBM WebSphere Adapter for Quick Start Tutorials

UN/CEFACT STANDARD BUSINESS DOCUMENT HEADER Technical Specification Version

Back Propagation Neural Networks User Manual

A User s Guide to ALMA Scheduling Blocks (Cycle 3)

Oracle SQL. Course Summary. Duration. Objectives

ITS. Java WebService. ITS Data-Solutions Pvt Ltd BENEFITS OF ATTENDANCE:

Easy CramBible Lab DEMO ONLY VERSION Test284,IBM WbS.DataPower SOA Appliances, Firmware V3.6.0

WEB SERVICES. Revised 9/29/2015

On Reproducible Econometric Research

IMAN: DATA INTEGRATION MADE SIMPLE YOUR SOLUTION FOR SEAMLESS, AGILE DATA INTEGRATION IMAN TECHNICAL SHEET

Discovering SQL. Wiley Publishing, Inc. A HANDS-ON GUIDE FOR BEGINNERS. Alex Kriegel WILEY

Qualys API Limits. July 10, Overview. API Control Settings. Implementation

Extracting Your Company s Data with the New Audit Data Standard

What is SOAP MTOM? How it works?

CONTRACT MODEL IPONZ DESIGN SERVICE VERSION 2. Author: Foster Moore Date: 20 September 2011 Document Version: 1.7

Server-Side Web Development JSP. Today. Web Servers. Static HTML Directives. Actions Comments Tag Libraries Implicit Objects. Apache.

WebSphere ESB Best Practices

Chapter 2 Database System Concepts and Architecture

Web. Services. Web Technologies. Today. Web. Technologies. Internet WWW. Protocols TCP/IP HTTP. Apache. Next Time. Lecture # Apache.

IBM SPSS Direct Marketing 23

Unified XML/relational storage March The IBM approach to unified XML/relational databases

Oracle Database 12c: Introduction to SQL Ed 1.1

TDAQ Analytics Dashboard

IBM SPSS Direct Marketing 22

A Sample OFBiz application implementing remote access via RMI and SOAP Table of contents

ArcSight Express Administration and Operations Course

Router Architectures

E-Invoicing Supplier Manual

Using Excel for Statistical Analysis

Generating XML from Relational Tables using ORACLE. by Selim Mimaroglu Supervisor: Betty O NeilO

Purpose What is EDI X EDI X12 standards and releases Trading Partner Requirements EDI X12 Dissected... 3

One Function, Two Approaches Document Management in OTM and GTM

REDUCING THE COST OF GROUND SYSTEM DEVELOPMENT AND MISSION OPERATIONS USING AUTOMATED XML TECHNOLOGIES. Jesse Wright Jet Propulsion Laboratory,

Three SOA Case Studies understanding what to use where. Paul Fremantle Chief Technology Officer WSO2 Inc

Satisfying business needs while maintaining the

What is in a Distributed Object System? Distributed Object Systems 5 XML-RPC / SOAP. Examples. Problems. HTTP protocol. Evolution

Author: Gennaro Frazzingaro Universidad Rey Juan Carlos campus de Mostòles (Madrid) GIA Grupo de Inteligencia Artificial

MPD Technical Webinar Transcript

13. Project Management and the Australian Bureau of Statistics: Doing What Works

<Insert Picture Here> Oracle SQL Developer 3.0: Overview and New Features

Crystal Converter User Guide

Functional Data Analysis of MALDI TOF Protein Spectra

Global Business Services and the Global Payroll Function

MS Designing and Optimizing Database Solutions with Microsoft SQL Server 2008

LiTH, Tekniska högskolan vid Linköpings universitet 1(7) IDA, Institutionen för datavetenskap Juha Takkinen

Requirements for a Long-term Viable, Archive Data Format

1. Comments on reviews a. Need to avoid just summarizing web page asks you for:

SQL Server Administrator Introduction - 3 Days Objectives

Terms and Definitions for CMS Administrators, Architects, and Developers

TopBraid Life Sciences Insight

Moving from ISO9000 to the Higher Levels of the Capability Maturity Model (CMM)

1. ERP integrators contacts. 2. Order export sample XML schema

Concepts of Database Management Seventh Edition. Chapter 9 Database Management Approaches

HOST EUROPE CLOUD STORAGE REST API DEVELOPER REFERENCE

: HP HP0-M28. : Implementing HP Asset Manager Software. Version : R6.1

NoSQL systems: introduction and data models. Riccardo Torlone Università Roma Tre

SPARROW Gateway. Developer API. Version 2.00

Setting up Dynamicweb for Load Balancing with Microsoft ARR for IIS8

Replacements TECHNICAL REFERENCE. DTCCSOLUTIONS Dec Copyright 2009 Depository Trust Clearing Corporation. All Rights Reserved.

Exam Name: Test284,IBM WbS.DataPower SOA

HP Application Lifecycle Management (ALM)

Schema documentation for types1.2.xsd

Spectral Line II. G ij (t) are calibrated as in chapter 5. To calibrated B ij (ν), observe a bright source that is known to be spectrally flat

Developing XML Solutions with JavaServer Pages Technology

Organizing Your Approach to a Data Analysis

Internet Working 5 th lecture. Chair of Communication Systems Department of Applied Sciences University of Freiburg 2004

Assessment Requirements for SITHGAM012 Conduct Roulette games

Accountability Brief

NEMSIS v3 Web Services Guide

What s new in Spring 3.1?

Best Practices: Extending Enterprise Applications to Mobile Devices

Who Doesn t Want to be Agile? By: Steve Dine President, Datasource Consulting, LLC 7/10/2008

LearnFromGuru Polish your knowledge

Datatype Channel p. 111 Invalid Message Channel p. 115 Dead Letter Channel p. 119 Guaranteed Delivery p. 122 Channel Adapter p. 127 Messaging Bridge

An Approach to Implement Map Reduce with NoSQL Databases

TopBraid Insight for Life Sciences

Archival Data Format Requirements

ARDA Experiment Dashboard

SAS Business Intelligence Online Training

SOA with Java. Realizing Service-Orientation with Java Technologies UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO

Transcription:

SDM Binary Data Format: Development, Specification & EVLA Issues WIDAR Correlator Face-to-face Meeting 2007 12 12, Socorro M. Pokorny

Where we are, and how we got there ALMA format; two documents: J. Pisano s descriptive correlator output document, and F. Viallefond s XML schemas. 1

Where we are, and how we got there ALMA format; two documents: J. Pisano s descriptive correlator output document, and F. Viallefond s XML schemas. Proposed WIDAR format; M. Pokorny adapted ALMA format with some modifications. 1

Where we are, and how we got there ALMA format; two documents: J. Pisano s descriptive correlator output document, and F. Viallefond s XML schemas. Proposed WIDAR format; M. Pokorny adapted ALMA format with some modifications. Format reconciliation involving J. McMullin, M. Rupen, J. Pisano, F. Viallefond, M. Pokorny. 1

Where we are, and how we got there ALMA format; two documents: J. Pisano s descriptive correlator output document, and F. Viallefond s XML schemas. Proposed WIDAR format; M. Pokorny adapted ALMA format with some modifications. Format reconciliation involving J. McMullin, M. Rupen, J. Pisano, F. Viallefond, M. Pokorny. Viallefond s continuing work on schemas and another descriptive document. 1

Where we are, and how we got there ALMA format; two documents: J. Pisano s descriptive correlator output document, and F. Viallefond s XML schemas. Proposed WIDAR format; M. Pokorny adapted ALMA format with some modifications. Format reconciliation involving J. McMullin, M. Rupen, J. Pisano, F. Viallefond, M. Pokorny. Viallefond s continuing work on schemas and another descriptive document. Common descriptive document written by Pokorny, based on Pisano s and Viallefond s work, and reviewed and modified by Pisano. 1

Where we are, and how we got there ALMA format; two documents: J. Pisano s descriptive correlator output document, and F. Viallefond s XML schemas. Proposed WIDAR format; M. Pokorny adapted ALMA format with some modifications. Format reconciliation involving J. McMullin, M. Rupen, J. Pisano, F. Viallefond, M. Pokorny. Viallefond s continuing work on schemas and another descriptive document. Common descriptive document written by Pokorny, based on Pisano s and Viallefond s work, and reviewed and modified by Pisano. Awaiting final round of schema modifications and document review by Viallefond. 1

Transition to common BDF Aggregation Integrations aggregated into a single file by sub-scan. Somewhat less flexible than previously proposed WIDAR format, but sufficient. No index section (could perhaps be slipped in on the sly). Common integration header information refactored into a sub-scan header. 2

Transition to common BDF Aggregation Integrations aggregated into a single file by sub-scan. Somewhat less flexible than previously proposed WIDAR format, but sufficient. No index section (could perhaps be slipped in on the sly). Common integration header information refactored into a sub-scan header. Axis lists adopted 2

Transition to common BDF Aggregation Integrations aggregated into a single file by sub-scan. Somewhat less flexible than previously proposed WIDAR format, but sufficient. No index section (could perhaps be slipped in on the sly). Common integration header information refactored into a sub-scan header. Axis lists adopted Attributes on spectral windows adopted 2

Transition to common BDF Aggregation Integrations aggregated into a single file by sub-scan. Somewhat less flexible than previously proposed WIDAR format, but sufficient. No index section (could perhaps be slipped in on the sly). Common integration header information refactored into a sub-scan header. Axis lists adopted Attributes on spectral windows adopted Non-standard MIME headers dropped 2

Transition to common BDF Aggregation Integrations aggregated into a single file by sub-scan. Somewhat less flexible than previously proposed WIDAR format, but sufficient. No index section (could perhaps be slipped in on the sly). Common integration header information refactored into a sub-scan header. Axis lists adopted Attributes on spectral windows adopted Non-standard MIME headers dropped Content-type for binary attachments corrected 2

Transition to common BDF Aggregation Integrations aggregated into a single file by sub-scan. Somewhat less flexible than previously proposed WIDAR format, but sufficient. No index section (could perhaps be slipped in on the sly). Common integration header information refactored into a sub-scan header. Axis lists adopted Attributes on spectral windows adopted Non-standard MIME headers dropped Content-type for binary attachments corrected Weights binary attachment with values in lookup table adopted 2

Elaboration beyond WIDAR Data processors The SDM BDF can accomodate many different data processor outputs, not only correlator outputs. Significant parts of the specification are devoted to describing possible format variations to allow for a variety of instruments. WIDAR backend ALMA-B correlator ACA correlator ALMA total power detector WIDAR wideband auto-correlations? 3

Elaboration beyond WIDAR Data processors The SDM BDF can accomodate many different data processor outputs, not only correlator outputs. Significant parts of the specification are devoted to describing possible format variations to allow for a variety of instruments. WIDAR backend ALMA-B correlator ACA correlator ALMA total power detector WIDAR wideband auto-correlations? Telescope-dependent constraints ALMA would like to include the limits on a variety of elements in the BDF into the XML schema that defines the header format. I have argued for their elimination. These limits are still included, and are, at the moment, hard-coded in the schema. 3

BDF documents Everything specifying the SDM BDF format will soon be in one project under revision control. One descriptive document with application-specific annotations as desired, and one appendix for each application. Descriptive document has link to applicable XML schema documents. 4

Questions Is the BDF required for RTDD? 5

Questions Is the BDF required for RTDD? Will the BDF be used for WIDAR wideband auto-correlation data? 5