Welcome

Building a diverse team to collaborate on the implementation, adoption, and education of these principals is critical. As such we'll be embracing STEAM; ensuring core competencies from diverse backgrounds are brought together. The common goal: improving our ability to semantically capture knowledge that enables reproducible research to drive collaboration on larger research questions.

Welcome to our collaborative blog to understand, design and communicate scientifically based engineering processes with mathmatical rigor while leveraging modern technology for human interactions and collaborations.  

Some may ask why?  To which we put forth our first assumption in that large research questions at hand in this century will increasingly rely on broader collaborations across academia, government and industry.  Research questions from health care, energy, and resource utilization (e.g., water consumption, greenhouse gas emissions) organizations are striving to share information and collaborate more effectively to bring solutions to key problems we face. 

We propose four fundamental idioms as central to the success of effective inter-community STEAM centric research collaborations.

Recent Activity

Filter 

Monday, September 18

Monday, September 11

Saturday, September 2

Tuesday, August 22

Sunday, August 13

Thursday, March 9

  • 8:10am
    Too many differences to list. See Revisions for details.
  • 8:09am
    ...
    Changes to Body
     
    System must hit a low price point
     
    System must hit a low price point
     
     
    -
    Some maybe stating that these user requirements are indeed to high level - but we must put these forth to ensure the design around functional requirements are bounded in long term strategy of costs, quality and agility.  Drilling a little deeper on these user requirements from a scientific and engineering perspective exposes some key architectural requirements nicely defined by a broad spectrum of users under the leadership of "Extremely Large Database" and published in this article ref [1].
    +
    Some maybe stating that these user requirements are indeed to high level - but we must put these forth to ensure the design around functional requirements are bounded in long term strategy of costs, quality and agility.  Drilling a little deeper on these user requirements from a scientific and engineering perspective exposes some key architectural requirements nicely defined by a broad spectrum of users under the leadership of "Extremely Large Database" and published in this article ref [1] - you can also see the SciDB work here [2].
     
    ARCHITECTURAL REQUIREMENTS ---------------------------------------------------
     
    ARCHITECTURAL REQUIREMENTS ---------------------------------------------------
     
     
     
     
     
    [1] http://madsciguys.org/?q=node/346
     
    [1] http://madsciguys.org/?q=node/346
      +
    [2] http://madsciguys.org/node/7075
    Read more
  • 8:06am
    No visible changes
    Read more