1 / 4

CSDMS communication and community

CSDMS communication and community. The rationale: ‘community input and involvement are essential to the success of CSDMS;’ time to ‘take stock of how our community currently functions and develop plans for the future’ What is the community?

eden
Télécharger la présentation

CSDMS communication and community

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSDMS communication and community • The rationale: • ‘community input and involvement are essential to the success of CSDMS;’ • time to ‘take stock of how our community currently functions and develop plans for the future’ • What is the community? • internal & external; developers vs. users; modelers vs. non-modelers • our vision for ideal communication depends on how this is defined… • and, this must be considered in designing 5-yr strategies • vision: • developers: contributing code to CSDMS is valuable & straightforward • users: finding and using CSDMS models is valuable & straightforward • modelers: significant advantages to modeling within the CSDMS • non-modelers: should be aware of, and not intimidated by using CSDMS • -or- everyone should use CSDMS

  2. challenges • multiple audiences require multiple tools/strategies • difficult for some potential users to climb the learning curve • ‘if you build it they will come’ • csdms continues to build (eg. first articles, CMT just becoming available) • difficult to communicate potential • convincing developers to run models with CSDMS/CMT • not just independently on own computers • some developers reluctant to give up source code • moving the scientific community towards coupled models • rather than focusing on a single setting/code • communicating ‘proper’ use of various models • developers are more aware of intended purposes and limitations

  3. possible strategies 1 • multiple audiences require multiple tools/strategies • improved documentation (help?) for submitting models (videos?) • CMT: more documentation? different architecture? additional version (CMT-lite)? • discussion boards on the CSDMS website (users helping users) • ‘if you build it they will come’ • encouraging acknowledgement of CSDMS • publications & presentations; member websites; in article reviews • increasing visibility of success stories • articles in EOS, Sedimentary Record, GSA Today? AAPG? • convincing developers to run models with CSDMS/CMT • communicate the value of CSDMS – promote prestige of contributing to CSDMS • traveling CSDMS lecturer? new awards for student modeling papers? • mentoring our students to write CSDMS-ready code, and to submit it (changing culture from bottom up)

  4. possible strategies 2 • moving the scientific community towards coupled models • promote the use coupled models (by using them; by highlighting them on the webpage and in pubs like EOS) • in particular, show utility of coupled models via timely use • eg. use coupled CEM and ocean circulation to look at remobilization of oiled sediments in GOM (just one idea) • communicating ‘proper’ use of various models • improving communication between developer and user (and amongst model users) • discussion board • developer is notified when his/her code is discussed • website redesign to address all of the above…

More Related