incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "ClimateModelDiagnosticAnalyzerProposal" by LeiPan
Date Sat, 28 Feb 2015 09:24:13 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "ClimateModelDiagnosticAnalyzerProposal" page has been changed by LeiPan:
https://wiki.apache.org/incubator/ClimateModelDiagnosticAnalyzerProposal?action=diff&rev1=15&rev2=16

  
  The proposed web-based tools let users display, analyze, and download earth science data
interactively. These tools help scientists quickly examine data to identify specific features,
e.g. trends, geographical distributions, etc., and determine whether a further study is needed.
All of the tools are designed and implemented to be general so that data from models, observation,
and reanalysis are processed and displayed in a unified way to facilitate fair comparisons.
The services prepare and display data as a colored map or an X-Y plot and allow users to download
the analyzed data. Basic visual capabilities include 1) displaying two-dimensional variable
as a map, zonal mean, and time series 2) displaying three-dimensional variable’s zonal mean,
a two-dimensional slice at a specific altitude, and a vertical profile. General analysis can
be done using the difference, scatter plot, and conditional sampling services. All the tools
support display options for using linear or logarithmic scales and allow users to specify
a temporal range and months in a year. The source/input datasets for these tools are CMIP5
model outputs, Obs4MIP observational datasets, and ECMWF reanalysis datasets, are stored in
the tool server, and are selectable by a user through the web services.
  
- 1. Two dimensional variable services
+ 1. '''Two dimensional variable services'''
  
  * Map of two-dimensional variable 
  
@@ -24, +24 @@

  
  This service displays the average of a two-dimensional variable over the specific region
as function of time as an X-Y plot.
  
- 2. Three dimensional variable services
+ 2. '''Three dimensional variable services'''
  
  * Map of a two dimensional slice of a three-dimensional variable
  
@@ -38, +38 @@

  
  Compute the area weighted average of a three-dimensional variable over the specified region
and display the average as function of pressure level (altitude) as an X-Y plot.
  
- 3. General services
+ 3. '''General services'''
  
  * Difference of two variables
  
@@ -58, +58 @@

  
  == Current Status ==
  
- The current version of AsterixDB was co-developed by a team of faculty, staff, and students
at UC Irvine and UC Riverside. The project was initiated as a large NSF-sponsored project
in 2009, the goal of which was to combine the best ideas from the parallel database world,
the then new Hadoop world, and the semi-structured (e.g., XML/JSON) data world in order to
create a next-generation BDMS. A first informal open source release was made four years later,
in June of 2013, under the Apache Software License 2.0.
+ The current version of Climate Model Diagnostic Analyzer was developed by a team at JPL.
The project was initiated as a large NASA-sponsored project in 2011, the goal of which was
to .
  
  == Meritocracy ==
  
@@ -66, +66 @@

  
  == Community ==
  
- While AsterixDB started as a university project it has developed into a community. A number
of the initial committers started contributing in academia and continue to actively participate
and contribute after graduation. And we seek to further develop developer and user communities.
One way to broaden the community that is ongoing is through academic collaborations (currently
with IIT Mumbai in India and TU Berlin in Germany). During incubation we will also explicitly
seek increased industrial participation.
+ While Climate Model Diagnostic Analyzer started as a JPL research project it has been used
in a summer school ... A number of the initial committers started contributing in academia
and continue to actively participate and contribute after graduation. And we seek to further
develop developer and user communities. One way to broaden the community that is ongoing is
through academic collaborations (currently with IIT Mumbai in India and TU Berlin in Germany).
During incubation we will also explicitly seek increased industrial participation.
  
  Some indicators of the effort's development community and history can be found at: https://www.openhub.net/p/asterixdb/contributors?query=&sort=commits_12_mo,
https://www.openhub.net/p/hyracks/contributors?query=&sort=commits_12_mo
  
  == Core Developers ==
  
- The core developers of the project are diverse, although initially UC Irvine heavy (roughly
50%) due to the project's origins at UCI. The other 50% are from other academic institutions
(UC Riverside and the Hebrew University in Jerusalem) and companies (Couchbase, IBM, KACST
Saudi Arabia, Oracle, Saudi Aramco, X15 Software).
+ The core developers of the project are JPL scientists and software developers. The other
50% are from other academic institutions (UC Riverside and the Hebrew University in Jerusalem)
and companies (Couchbase, IBM, KACST Saudi Arabia, Oracle, Saudi Aramco, X15 Software).
  
  == Alignment ==
  
@@ -80, +80 @@

  
  There are also a number of related Apache projects and dependencies that will be mentioned
below in the Relationships with Other Apache products section.
  
+ 
+ 
+ == Known Risks ==
+ 
+ === Orphaned products ===
+ 
+ Given the current level of intellectual investment in AsterixDB, the risk of the project
being abandoned is very small. The UCI/UCR faculty team leads are highly incentivized to continue
development since the database groups at UC Irvine and UC Riverside are both reliant on AsterixDB
as a platform for long-term graduate research projects. UC San Diego is also beginning to
contribute to the code base, and a collaboration involving public health applications is forming
with UCLA. The work on AsterixDB is managed via a mix of mailing list discussions supplemented
by weekly project status meetings which are summarized on the mailing list. Typical (local
plus Skype-in) attendance to the weekly status meetings runs at about 20 active contributors.
+ 
+ === Inexperience with Open Source ===
+ 
+ AsterixDB and Hyracks were completely developed in Open Source under the ALv2. The source
code repositories, issue tracker, and mailing lists are available on Google Code and discussions
and decisions happen on the mailing lists (which is necessary due to the geographic distribution
of the current developers).
+ 
+ Also a few of the initial committers have contributed to Apache projects. Vinayak Borkar
is a committer on the Apache Helix and Apache VXQuery projects. Till Westmann is the VP VXQuery
at the ASF and an IPMC member. Preston Carman and Steven Jacobs are committers on the Apache
VXQuery project.
+ 
+ === Relationships with Other Apache Products ===
+ 
+ Apache VXQuery is based on the Hyracks data-parallel runtime, which is also included in
the AsterixDB code base.
+ 
+ AsterixDB is closely related to Apache Hadoop. Included in AsterixDB is support for accessing
external data in HDFS (and Hive formats), and resource management and system administration
features are in the process of being migrated to YARN.
+ 
+ AsterixDB's AQL query facilities offer comparable query power to Apache's Pig and Hive systems
for big data analytics. AsterixDB differs in storing and indexing data and thus being able
to quickly answer small and medium queries without large HDFS data scans - thereby targeting
a different class of use cases.
+ 
+ AsterixDB's data storage and indexing facilities are similar to those of HBase, but AsterixDB
differs in being a much more complete and queryable BDMS (not just a key-value style store).
+ 
+ AsterixDB's target use cases are not in-memory processing or iterative algorithm support,
making AsterixDB complementary to the Apache Spark platform. (Spark interoperability is on
our longer-term to-do wishlist.)
+ 
+ === Homogeneous Developers ===
+ 
+ As mentioned before the current community is already organizationally and geographically
distributed - and we would like to increase the heterogeneity.
+ 
+ === Reliance on Salaried Developers ===
+ 
+ Of the initial committers only 3 are full-time UCI staff. The other committers are a mix
of students, alumni who continue to contribute to the effort, and individuals working with
permission part-time (or in spare time) on this project.
+ 
+ === A Excessive Fascination with the Apache Brand ===
+ 
+ We believe in the processes, systems, and framework Apache has put in place. Apache is also
known to foster a great community around their projects and provide exposure. While brand
is important, our fascination with it is not excessive. We believe that the ASF is the right
home for AsterixDB and that having AsterixDB inside of the ASF will lead to a better long-term
outcome for the Big Data community.
+ 
+ === Documentation ===
+ 
+ Documentation and publications related to AsterixDB can be found at http://asterixdb.ics.uci.edu/.
+ 
+ === Initial Source ===
+ 
+ Current source resides in Google code: https://code.google.com/p/asterixdb/ (query language
and upper system layers) and https://code.google.com/p/hyracks/ (dataflow runtime system and
storage management libraries).
+ 
+ === External Dependencies ===
+ 
+ AsterixDB depends on a number of Apache projects:
+ 
+ Ant
+ Avro
+ ApacheDB JDO
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message