<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Lindsey Heagy on Medium]]></title>
        <description><![CDATA[Stories by Lindsey Heagy on Medium]]></description>
        <link>https://medium.com/@lheagy?source=rss-3807e220bc10------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*7fIgIcW1PUZDDQMIjzdwjQ.jpeg</url>
            <title>Stories by Lindsey Heagy on Medium</title>
            <link>https://medium.com/@lheagy?source=rss-3807e220bc10------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:22:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lheagy/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Jupyter meets the Earth: EarthCube Community Meeting]]></title>
            <link>https://medium.com/pangeo/jupyter-meets-the-earth-earthcube-community-meeting-ab32f5c91caf?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab32f5c91caf</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[geoscience]]></category>
            <category><![CDATA[jupyter]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Wed, 19 Aug 2020 18:40:10 GMT</pubDate>
            <atom:updated>2020-09-11T00:34:07.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*h1CnyqyQk9K9crjW.png" /></figure><p><em>By: Lindsey Heagy, Fernando Pérez, Joe Hamman and the Jupyter meets the Earth team </em>(cross-posted on the <a href="https://blog.jupyter.org/jupyter-meets-the-earth-earthcube-community-meeting-4bb9fb49cada?source=friends_link&amp;sk=ecec9c45937c0e354bed03fc13dc0b92">Jupyter blog</a>)</p><p>As a part of the <a href="https://www.earthcube.org/EC2020">2020 EarthCube annual meeting</a>, we held a <a href="https://blog.jupyter.org/jupyter-meets-the-earth-1b0eb33c83f?source=friends_link&amp;sk=945065ffe0c101b6c8ec369425574600"><em>Jupyter meets the Earth</em></a> community discussion session on July 27. The Jupyter meets the Earth project is an EarthCube funded effort that combines research use cases in geosciences with technical developments within the Jupyter and Pangeo ecosystems. In this model of equal partners, scientific questions help drive software infrastructure development, and new technologies expand the horizons of viable research. This online workshop was an opportunity to gather members of the community, welcome newcomers, provide updates on the Jupyter and Pangeo ecosystems, and have time for discussion.</p><p>The goals for the meeting were to:</p><ul><li>Provide an overview of the Jupyter &amp; Pangeo ecosystems for researchers from the EarthCube community.</li><li>Outline avenues for getting involved.</li><li>Gather input for what advancements would best serve your research needs.</li></ul><p>Over 100 participants registered, and we had contributions from 9 speakers. The meeting was a mix of presentations and Q&amp;A from the community. The full recording of the meeting is available on <a href="https://youtu.be/Zj3Gm4LNfwo">youtube</a>, and we encourage continued discussion on the <a href="https://discourse.pangeo.io/t/jupyter-meets-the-earth-earthcube-meeting-july-27/689">associated discourse post</a>.</p><h3>Presentations (<a href="https://drive.google.com/drive/folders/1lyIJcqHKqhstrnQU5ZWEgSsTRbVjpkZn?usp=sharing">google drive folder</a>)</h3><p>Fernando Pérez (<a href="https://docs.google.com/presentation/d/1oR-LmqSkUsFUZBWH4qz1TDnRzd2oWHxUXgYxqjUb3LY/edit?usp=sharing">slides</a>) started off the meeting by introducing the <em>Jupyter meets the Earth</em> project — an effort aimed at driving forward technological developments in the Jupyter and Pangeo ecosystems in partnership with researchers in the geosciences. The motivation is to advance research and the software that supports it by combining domain expertise with methods in data science, software &amp; data engineering practices. He provided an overview of Project Jupyter, highlighting the interplay between software and content, services, standards, community and governance that is necessary for broad-impact scientific open source software projects. He presented the extensible <a href="https://jupyterlab.readthedocs.io/en/stable/">JupyterLab</a> platform, that can be adapted to domain-specific needs as illustrated by the <a href="http://www.bionet.ee.columbia.edu/research/ffbo/fbl">FlyBrainLab</a> and <a href="https://blog.jupyter.org/jupyterlab-ros-3dc9dab7f421">Cloud Robotics Command Station</a> efforts. The <em>Jupyter meets the Earth</em> team aims to similarly develop tools and extensions that will support interactive computing workflows in the geosciences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmsFWNwWDW9-8jtDOa6_RQ.png" /><figcaption>Overview of Jupyter and Jupyter meets the Earth from Fernando Pérez</figcaption></figure><p>Next up, Scott Henderson (<a href="https://docs.google.com/presentation/d/1pdlUGRrX46kJYZHTkGA6HuOYHQ_Yt2NNxQlLpRFB9jo/edit?usp=sharing">slides</a>) provided an overview of Pangeo and associated community events, including Hackweeks. “Pangeo is first and foremost a community promoting open, reproducible, and scalable science.” In terms of technology, this involves developing fully open source tools that can be deployed on shared computational infrastructure, such as HPC centers or the cloud, and hosting several forums to foster communication between scientists and software developers. Software is an important avenue for connection, but the overarching goals are a rallying point for a community. The critical mass of enthusiastic people has been key to the success of the Pangeo model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOlTcY7mi7kIKT22Kc2_bw.png" /><figcaption>Overview of Pangeo and Hackweeks from <a href="https://medium.com/u/a2ec3bba4164">Scott Henderson</a></figcaption></figure><p>The Pangeo model is intended for use both on the cloud and on High Performance Computing (HPC) infrastructure. Kevin Paul gave the third talk on Pangeo on HPC (<a href="https://docs.google.com/presentation/d/1eKDCK25jxjSFixwQX9GW56w84ZpaxRywEvMMYuX3Tg8/edit?usp=sharing">slides</a>, <a href="https://binder.pangeo.io/v2/gh/pangeo-data/pangeo-tutorial-agu-2018/master?filepath=notebooks%2Fgmet_ensemble.ipynb">notebook</a>). HPC and cloud computing environments present technical differences in terms of usage patterns, file access, and resource allocations, however, the goals of Jupyter and Pangeo are similar in both cases — to enable interactive computing and simplify the user experience on both. Tools such as <a href="https://dask.org/">dask</a> and <a href="https://kubernetes.dask.org/en/latest/">dask-kubernetes</a>/<a href="https://jobqueue.dask.org/en/latest/index.html">dask-jobqueue</a> are targeted at enabling parallel computing on both infrastructures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofmEc1YhrAqvCs3FXhuI2g.png" /><figcaption>Kevin Paul giving us a demo of Pangeo on the Cheyenne supercomputer</figcaption></figure><p>After a Q&amp;A session that included questions on the computational cost of running Pangeo Infrastructure and efficient use of tools including Zarr, we moved on to a series of lightning talks.</p><h3>Lightning Talks</h3><p>Six speakers presented short lightning talks on aspects of the Jupyter and Pangeo ecosystems ranging from technologies to scientific applications to opportunities to engage with the Pangeo community.</p><p>Anderson Banihirwe (<a href="https://gist.github.com/andersy005/e08891883d91c01ab0ce963046d86343#file-intake-jupyter-meets-earth-ipynb">notebook</a> and details in <a href="https://github.com/earthcube2020/ec20_banihirwe_etal">intake-esm</a>) kicked off the lightning talks by giving a demo and overview of Intake — a project to streamline loading and sharing of data. He showed a demo that included both Optimum Interpolation Sea Surface Temperature (OISST) data, as well as data from the Coupled Model Intercomparison Project (CMIP) running interactively on Cheyenne, the supercomputer at NCAR and using Dask for distributing the workload across nodes, with real-time diagnostics of the distributed computation provided by <a href="https://github.com/dask/dask-labextension">Dask’s JupyterLab extension</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cCp6QLc_60xWGsAN" /><figcaption>Demo from <a href="https://medium.com/u/bc2b9ddd350c">Anderson Banihirwe</a> using intake to access OSSIT and CMIP data</figcaption></figure><p>Next up, Scott Dale Peckham (<a href="https://github.com/peckhams/balto_gui">notebook</a>) gave a presentation that demonstrated the use of ipywidgets and ipyleaflet to create an interactive interface for fast access to geoscience data on servers that support the OpenDAP protocol. The project he champions is called <a href="https://cires.colorado.edu/research/research-groups/project/balto-earthcube-brokered-alignment-long-tail-observations">BALTO, the Brokered Alignment of Long Tail Observations</a> (also a famous Siberian Husky and sled dog). These graphical interface elements can be used in a programmatic workflow such as a Jupyter Notebook, but they conveniently encapsulate many details of accessing the data and resources provided by BALTO. This allows the scientists to focus on their research questions, without having to break their workflow to access data with external tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Esr4Ec_RKwqx2la7G9eDFg.png" /><figcaption>BALTO GUI demo from Scott Peckham</figcaption></figure><p>We then had a talk from Edom Moges (<a href="https://docs.google.com/presentation/d/1QUdRZEI84jq9PoBEucnrdHkReghYrEg-jjGJZWzVvJA/edit?usp=sharing">slides</a>) who presented work he is conducting with Laurel Larsen’s research group in hydrology as one use case in the Jupyter meets the Earth project. The presentation focused on a data synthesis work that aims to build a Jupyter based interactive platform that transforms raw hydrometeorological data to a gap-filled ready to use data for several intensively monitored watersheds across the US. The platform will be a basis for future community initiatives to benchmark data processing approaches, support comparative hydrological studies and comprehensive data-driven forecasts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPOqGuk9hRBV2WCl5QATIg.png" /><figcaption>Lightning talk from Edom Moges and Laurel Larsen on the hydrology use-case in the Jupyter meets the Earth project</figcaption></figure><p>Georgiana Dolocan (<a href="https://drive.google.com/file/d/1yu7gnRkHXkNhefVoBiho_Sl-C_7f0l85/view">video</a>) impressed us next with an animated video accompanied with her narration to explain JupyterHub, its components (authenticator, spawner, proxy) as well as deployment options. The littlest JupyterHub (TLJH) is designed to make it simple to deploy multi-user Jupyter infrastructure on a single machine, and the more sophisticated Zero 2 JupyterHub Kubernetes (Z2JH) option is meant to scale to many users and large computational needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c1JTc_WrA5t1oUgnvvtcKA.png" /><figcaption>Animations from <a href="https://medium.com/u/89845d7ac171">Georgiana Dolocan</a> on JupyterHub</figcaption></figure><p>Presenting from the perspective of an enthusiastic user, Erik Sundell (<a href="https://docs.google.com/presentation/d/1TafZRXouz57SRBonHGt6bogwQp5_kVrTP1RkpkO0xB8/edit?usp=sharing">slides</a>) gave us an overview of <a href="http://jupyterbook.org/">Jupyter Book</a>: a tool to quickly create beautiful websites from notebooks and markdown. He walked through how to host them for free online in a time efficient way, and highlighted features including connections to Binder, which enable users to run content interactively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfKDEmbHLgt-3eJlRqClaw.png" /><figcaption>Overview of JupyterBook from <a href="https://medium.com/u/f4824e86b5f8">Erik Sundell</a></figcaption></figure><p>Joe Hamman (<a href="https://docs.google.com/presentation/d/1GKVLUsa971FHZkPDhdTSgxZQralWyy-292aIg1tFY64/edit?usp=sharing">slides</a>) finished off our lightning talk session by outlining avenues for connecting with the Pangeo community. These include day-to-day communication on GitHub, Gitter, discourse and twitter, as well as more recent coffee-breaks. Depending on your topic of interest, there are also working groups that you can join on topics including data, machine learning, education, cloud computing, or you can suggest your own!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOkrUZhvWq5ywRPlaQ8QDA.png" /><figcaption>Connecting with the Pangeo community — an overview from <a href="https://medium.com/u/df9f03847f67">Joe Hamman</a></figcaption></figure><h3>Follow up and further discussion</h3><p>To continue the discussion afterwards, we posed (<a href="https://docs.google.com/presentation/d/1UqRd34zeOa5cW3aXFsjjh3TprgEHDl1cf4n1_BZezls/edit?usp=sharing">slides</a>) a few questions where we hope to learn from the community’s needs, such as:</p><ul><li>What does your interactive computing workflow look like today? What do you envision it will be in 5 years?</li><li>How would you like to publish and share your computational research and where can improvements be made?</li><li>How do you stay up to date with the evolving open-source ecosystem? How would you like to be keeping up-to-date?</li></ul><p>We are looking for your input and ideas! Please add your thoughts to the <a href="https://discourse.pangeo.io/t/jupyter-meets-the-earth-earthcube-meeting-july-27/689">discourse post</a>.</p><h3>Thanks</h3><p>Thank you to the participants, speakers, and especially Lynne Schreiber and Ouida Meier from the EarthCube office for all of their support and work (even with very last-minute requests!).</p><p>This work is part of the <em>Jupyter meets the Earth</em> project, supported by the NSF EarthCube program under awards <a href="https://www.nsf.gov/awardsearch/showAward?AWD_ID=1928406">1928406</a>, <a href="https://www.nsf.gov/awardsearch/showAward?AWD_ID=1928374">1928374</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZj3Gm4LNfwo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZj3Gm4LNfwo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZj3Gm4LNfwo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7b044cc7fca1698649b9d638f207c6e/href">https://medium.com/media/c7b044cc7fca1698649b9d638f207c6e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab32f5c91caf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pangeo/jupyter-meets-the-earth-earthcube-community-meeting-ab32f5c91caf">Jupyter meets the Earth: EarthCube Community Meeting</a> was originally published in <a href="https://medium.com/pangeo">pangeo</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jupyter meets the Earth: EarthCube Community Meeting]]></title>
            <link>https://medium.com/jupyter-blog/jupyter-meets-the-earth-earthcube-community-meeting-4bb9fb49cada?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/4bb9fb49cada</guid>
            <category><![CDATA[geoscience]]></category>
            <category><![CDATA[open-source-software]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[pangeo]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Mon, 17 Aug 2020 19:42:47 GMT</pubDate>
            <atom:updated>2020-09-11T00:32:26.693Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*h1CnyqyQk9K9crjW.png" /></figure><p><em>By: Lindsey Heagy, Fernando Pérez, Joe Hamman and the Jupyter meets the Earth team </em>(cross-posted on the <a href="https://medium.com/pangeo/jupyter-meets-the-earth-earthcube-community-meeting-ab32f5c91caf">Pangeo Blog</a>)</p><p>As a part of the <a href="https://www.earthcube.org/EC2020">2020 EarthCube annual meeting</a>, we held a <a href="https://blog.jupyter.org/jupyter-meets-the-earth-1b0eb33c83f?source=friends_link&amp;sk=945065ffe0c101b6c8ec369425574600"><em>Jupyter meets the Earth</em></a> community discussion session on July 27. The Jupyter meets the Earth project is an EarthCube funded effort that combines research use cases in geosciences with technical developments within the Jupyter and Pangeo ecosystems. In this model of equal partners, scientific questions help drive software infrastructure development, and new technologies expand the horizons of viable research. This online workshop was an opportunity to gather members of the community, welcome newcomers, provide updates on the Jupyter and Pangeo ecosystems, and have time for discussion.</p><p>The goals for the meeting were to:</p><ul><li>Provide an overview of the Jupyter &amp; Pangeo ecosystems for researchers from the EarthCube community.</li><li>Outline avenues for getting involved.</li><li>Gather input for what advancements would best serve your research needs.</li></ul><p>Over 100 participants registered, and we had contributions from 9 speakers. The meeting was a mix of presentations and Q&amp;A from the community. The full recording of the meeting is available on <a href="https://youtu.be/Zj3Gm4LNfwo">youtube</a>, and we encourage continued discussion on the <a href="https://discourse.pangeo.io/t/jupyter-meets-the-earth-earthcube-meeting-july-27/689">associated discourse post</a>.</p><h3>Presentations (<a href="https://drive.google.com/drive/folders/1lyIJcqHKqhstrnQU5ZWEgSsTRbVjpkZn?usp=sharing">google drive folder</a>)</h3><p>Fernando Pérez (<a href="https://docs.google.com/presentation/d/1oR-LmqSkUsFUZBWH4qz1TDnRzd2oWHxUXgYxqjUb3LY/edit?usp=sharing">slides</a>) started off the meeting by introducing the <em>Jupyter meets the Earth</em> project — an effort aimed at driving forward technological developments in the Jupyter and Pangeo ecosystems in partnership with researchers in the geosciences. The motivation is to advance research and the software that supports it by combining domain expertise with methods in data science, software &amp; data engineering practices. He provided an overview of Project Jupyter, highlighting the interplay between software and content, services, standards, community and governance that is necessary for broad-impact scientific open source software projects. He presented the extensible <a href="https://jupyterlab.readthedocs.io/en/stable/">JupyterLab</a> platform, that can be adapted to domain-specific needs as illustrated by the <a href="http://www.bionet.ee.columbia.edu/research/ffbo/fbl">FlyBrainLab</a> and <a href="https://blog.jupyter.org/jupyterlab-ros-3dc9dab7f421">Cloud Robotics Command Station</a> efforts. The <em>Jupyter meets the Earth</em> team aims to similarly develop tools and extensions that will support interactive computing workflows in the geosciences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmsFWNwWDW9-8jtDOa6_RQ.png" /><figcaption>Overview of Jupyter and Jupyter meets the Earth from Fernando Pérez</figcaption></figure><p>Next up, Scott Henderson (<a href="https://docs.google.com/presentation/d/1pdlUGRrX46kJYZHTkGA6HuOYHQ_Yt2NNxQlLpRFB9jo/edit?usp=sharing">slides</a>) provided an overview of Pangeo and associated community events, including Hackweeks. “Pangeo is first and foremost a community promoting open, reproducible, and scalable science.” In terms of technology, this involves developing fully open source tools that can be deployed on shared computational infrastructure, such as HPC centers or the cloud, and hosting several forums to foster communication between scientists and software developers. Software is an important avenue for connection, but the overarching goals are a rallying point for a community. The critical mass of enthusiastic people has been key to the success of the Pangeo model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VOlTcY7mi7kIKT22Kc2_bw.png" /><figcaption>Overview of Pangeo and Hackweeks from <a href="https://medium.com/u/a2ec3bba4164">Scott Henderson</a></figcaption></figure><p>The Pangeo model is intended for use both on the cloud and on High Performance Computing (HPC) infrastructure. Kevin Paul gave the third talk on Pangeo on HPC (<a href="https://docs.google.com/presentation/d/1eKDCK25jxjSFixwQX9GW56w84ZpaxRywEvMMYuX3Tg8/edit?usp=sharing">slides</a>, <a href="https://binder.pangeo.io/v2/gh/pangeo-data/pangeo-tutorial-agu-2018/master?filepath=notebooks%2Fgmet_ensemble.ipynb">notebook</a>). HPC and cloud computing environments present technical differences in terms of usage patterns, file access, and resource allocations, however, the goals of Jupyter and Pangeo are similar in both cases — to enable interactive computing and simplify the user experience on both. Tools such as <a href="https://dask.org/">dask</a> and <a href="https://kubernetes.dask.org/en/latest/">dask-kubernetes</a>/<a href="https://jobqueue.dask.org/en/latest/index.html">dask-jobqueue</a> are targeted at enabling parallel computing on both infrastructures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofmEc1YhrAqvCs3FXhuI2g.png" /><figcaption>Kevin Paul giving us a demo of Pangeo on the Cheyenne supercomputer</figcaption></figure><p>After a Q&amp;A session that included questions on the computational cost of running Pangeo Infrastructure and efficient use of tools including Zarr, we moved on to a series of lightning talks.</p><h3>Lightning Talks</h3><p>Six speakers presented short lightning talks on aspects of the Jupyter and Pangeo ecosystems ranging from technologies to scientific applications to opportunities to engage with the Pangeo community.</p><p>Anderson Banihirwe (<a href="https://gist.github.com/andersy005/e08891883d91c01ab0ce963046d86343#file-intake-jupyter-meets-earth-ipynb">notebook</a> and details in <a href="https://github.com/earthcube2020/ec20_banihirwe_etal">intake-esm</a>) kicked off the lightning talks by giving a demo and overview of Intake — a project to streamline loading and sharing of data. He showed a demo that included both Optimum Interpolation Sea Surface Temperature (OISST) data, as well as data from the Coupled Model Intercomparison Project (CMIP) running interactively on Cheyenne, the supercomputer at NCAR and using Dask for distributing the workload across nodes, with real-time diagnostics of the distributed computation provided by <a href="https://github.com/dask/dask-labextension">Dask’s JupyterLab extension</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cCp6QLc_60xWGsAN" /><figcaption>Demo from <a href="https://medium.com/u/bc2b9ddd350c">Anderson Banihirwe</a> using intake to access OSSIT and CMIP data</figcaption></figure><p>Next up, Scott Dale Peckham (<a href="https://github.com/peckhams/balto_gui">notebook</a>) gave a presentation that demonstrated the use of ipywidgets and ipyleaflet to create an interactive interface for fast access to geoscience data on servers that support the OpenDAP protocol. The project he champions is called <a href="https://cires.colorado.edu/research/research-groups/project/balto-earthcube-brokered-alignment-long-tail-observations">BALTO, the Brokered Alignment of Long Tail Observations</a> (also a famous Siberian Husky and sled dog). These graphical interface elements can be used in a programmatic workflow such as a Jupyter Notebook, but they conveniently encapsulate many details of accessing the data and resources provided by BALTO. This allows the scientists to focus on their research questions, without having to break their workflow to access data with external tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Esr4Ec_RKwqx2la7G9eDFg.png" /><figcaption>BALTO GUI demo from Scott Peckham</figcaption></figure><p>We then had a talk from Edom Moges (<a href="https://docs.google.com/presentation/d/1QUdRZEI84jq9PoBEucnrdHkReghYrEg-jjGJZWzVvJA/edit?usp=sharing">slides</a>) who presented work he is conducting with Laurel Larsen’s research group in hydrology as one use case in the Jupyter meets the Earth project. The presentation focused on a data synthesis work that aims to build a Jupyter based interactive platform that transforms raw hydrometeorological data to a gap-filled ready to use data for several intensively monitored watersheds across the US. The platform will be a basis for future community initiatives to benchmark data processing approaches, support comparative hydrological studies and comprehensive data-driven forecasts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPOqGuk9hRBV2WCl5QATIg.png" /><figcaption>Lightning talk from Edom Moges and Laurel Larsen on the hydrology use-case in the Jupyter meets the Earth project</figcaption></figure><p>Georgiana Dolocan (<a href="https://drive.google.com/file/d/1yu7gnRkHXkNhefVoBiho_Sl-C_7f0l85/view">video</a>) impressed us next with an animated video accompanied with her narration to explain JupyterHub, its components (authenticator, spawner, proxy) as well as deployment options. The littlest JupyterHub (TLJH) is designed to make it simple to deploy multi-user Jupyter infrastructure on a single machine, and the more sophisticated Zero 2 JupyterHub Kubernetes (Z2JH) option is meant to scale to many users and large computational needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c1JTc_WrA5t1oUgnvvtcKA.png" /><figcaption>Animations from <a href="https://medium.com/u/89845d7ac171">Georgiana Dolocan</a> on JupyterHub</figcaption></figure><p>Presenting from the perspective of an enthusiastic user, Erik Sundell (<a href="https://docs.google.com/presentation/d/1TafZRXouz57SRBonHGt6bogwQp5_kVrTP1RkpkO0xB8/edit?usp=sharing">slides</a>) gave us an overview of <a href="http://jupyterbook.org/">Jupyter Book</a>: a tool to quickly create beautiful websites from notebooks and markdown. He walked through how to host them for free online in a time efficient way, and highlighted features including connections to Binder, which enable users to run content interactively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfKDEmbHLgt-3eJlRqClaw.png" /><figcaption>Overview of JupyterBook from <a href="https://medium.com/u/f4824e86b5f8">Erik Sundell</a></figcaption></figure><p>Joe Hamman (<a href="https://docs.google.com/presentation/d/1GKVLUsa971FHZkPDhdTSgxZQralWyy-292aIg1tFY64/edit?usp=sharing">slides</a>) finished off our lightning talk session by outlining avenues for connecting with the Pangeo community. These include day-to-day communication on GitHub, Gitter, discourse and twitter, as well as more recent coffee-breaks. Depending on your topic of interest, there are also working groups that you can join on topics including data, machine learning, education, cloud computing, or you can suggest your own!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOkrUZhvWq5ywRPlaQ8QDA.png" /><figcaption>Connecting with the Pangeo community — an overview from <a href="https://medium.com/u/df9f03847f67">Joe Hamman</a></figcaption></figure><h3>Follow up and further discussion</h3><p>To continue the discussion afterwards, we posed (<a href="https://docs.google.com/presentation/d/1UqRd34zeOa5cW3aXFsjjh3TprgEHDl1cf4n1_BZezls/edit?usp=sharing">slides</a>) a few questions where we hope to learn from the community’s needs, such as:</p><ul><li>What does your interactive computing workflow look like today? What do you envision it will be in 5 years?</li><li>How would you like to publish and share your computational research and where can improvements be made?</li><li>How do you stay up to date with the evolving open-source ecosystem? How would you like to be keeping up-to-date?</li></ul><p>We are looking for your input and ideas! Please add your thoughts to the <a href="https://discourse.pangeo.io/t/jupyter-meets-the-earth-earthcube-meeting-july-27/689">discourse post</a>.</p><h3>Thanks</h3><p>Thank you to the participants, speakers, and especially Lynne Schreiber and Ouida Meier from the EarthCube office for all of their support and work (even with very last-minute requests!).</p><p>This work is part of the <em>Jupyter meets the Earth</em> project, supported by the NSF EarthCube program under awards <a href="https://www.nsf.gov/awardsearch/showAward?AWD_ID=1928406">1928406</a>, <a href="https://www.nsf.gov/awardsearch/showAward?AWD_ID=1928374">1928374</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FZj3Gm4LNfwo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DZj3Gm4LNfwo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FZj3Gm4LNfwo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c7b044cc7fca1698649b9d638f207c6e/href">https://medium.com/media/c7b044cc7fca1698649b9d638f207c6e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4bb9fb49cada" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jupyter-blog/jupyter-meets-the-earth-earthcube-community-meeting-4bb9fb49cada">Jupyter meets the Earth: EarthCube Community Meeting</a> was originally published in <a href="https://medium.com/jupyter-blog">Jupyter Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SimPEG release of 0.14]]></title>
            <link>https://medium.com/simpeg/simpeg-release-of-0-14-d67d81a654cb?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/d67d81a654cb</guid>
            <category><![CDATA[geophysics]]></category>
            <category><![CDATA[inversion]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[simulation]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Thu, 28 May 2020 00:34:03 GMT</pubDate>
            <atom:updated>2020-05-28T00:34:03.029Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>Lindsey Heagy, Joe Capriotti, and the SimPEG team</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L6PYdSn5NYIGUCn7iBdQuA.png" /></figure><p>We merged a big pull request into SimPEG this week (<a href="https://github.com/simpeg/simpeg/pull/786">#786</a>): over 30,000 lines of code changed! (and now close to 60,000 because we ran black 😉) These changes have been in progress since Summer 2019 and involved input, feedback, contributions, and improvements from many in the team. Normally, we push to have smaller pull-requests with tightly scoped changes, but this was a big refactor touching much of the code-base, and also includes major improvements and additions to the documentation, so we consolidated all of the changes and are releasing them to the world 🚀.</p><p>In this post, we will summarize some of the major changes and improvements as well as provide avenues for discussion and help if you are looking to migrate your code or want to get started with SimPEG.</p><h3>TL; DR</h3><p>SimPEG used to look a bit like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Ycjuzp2syAZOfOgH" /></figure><p>And now it looks sort of like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QLJuR1BlEpcMMU6I" /></figure><p>(We are actively having conversations on <a href="http://slack.simpeg.xyz/">Slack</a> about the most effective way to communicate the structure of the framework, please feel free to contribute your sketches and ideas!)</p><p>The major changes are:</p><ul><li>The Problem and Survey classes have been refactored into the Simulation and a much lighter-weight Survey</li><li>The Data class now plays an explicit role in the framework</li><li>Many classes and methods have been renamed to be more in-line with <a href="https://www.python.org/dev/peps/pep-0008/">PEP8 recommendations</a></li><li>There are efficiency improvements, including a first implementation using dask to parallelize aspects of the DC, IP and potential fields codes.</li><li>For help migrating your codes or if you have questions about the refactor, please post on <a href="https://simpeg.discourse.group/t/simulation-refactor-and-simpeg-0-14/110">discourse</a>.</li></ul><p>To get the latest code</p><pre>&gt; conda install -c conda-forge simpeg&gt;=0.14.0</pre><h3>Motivation</h3><p>In our post about the <a href="https://medium.com/simpeg/team-meeting-in-montreal-aad61ecdea8d?source=friends_link&amp;sk=f5f37a39250746b55380b919b79bdcb0">team meeting in Montreal</a> we outlined some challenges with the current structure of the SimPEG framework (original issue here: <a href="https://github.com/simpeg/simpeg/issues/562">#562</a>) primarily around the way we constructed a forward simulation. The pair method used to combine a problem which contained the physics-engine and a survey which contained the survey geometry made it tricky to interface to other simulation codes (and also was tough to explain — which is a good test of an architecture). Also, it wasn’t necessarily obvious where you bring your field data into the framework.</p><p>Since we started SimPEG in 2013, the Python ecosystem has advanced significantly. <a href="https://dask.org/">Dask</a> did not yet exist, nor did the <a href="http://pangeo.io/">Pangeo</a> community, which has been an important catalyst for scalable computational technology and a community of practice in the geosciences. Undertaking a major refactor is also a chance to think through how to interoperate and build upon the advancements made by these groups.</p><h3>Significant changes — the highlights</h3><p>We provide a detailed overview of the changes in the <a href="http://docs.simpeg.xyz/content/release/0.14.0-notes.html">release notes</a>, so here we will share some of the highlights.</p><h4>No more problem’s</h4><p>The name of the Problem class has been changed to Simulation and now the Simulation contains all of the methods you expect a forward simulation to perform including computing a solution to a Partial Differential Equation (PDE) (the fields method) and generating predicted data (the dpred method). Previously these were divided up between the Problem and the Survey; the Problem had the fields method while the Survey had the dpred method (This is why we used to need that pair method, so that the Survey and Problem each had access to the methods and properties of the other).</p><p>The Survey is now a much lighter weight class; it contains a source_list with each source having its own receiver_list as before (and see how nice the PEP8 names look as compared to srcList and rxList 😃) and is now no longer needs to be paired.</p><p>What does this mean for your code? Previously, computing fields and predicted data in a DC-resistivity simulation would have looked like this</p><pre>survey = DC.Survey(source_list)<br>prob = DC.Problem3D_CC(mesh, rhoMap=mapping)<br>prob.pair(survey)</pre><pre># compute the fields and predicted data<br># if you don’t want to view the fields, predicted data can be<br># computed in one step survey.dpred(model)<br>fields = prob.fields(model)<br>dpred = survey.dpred(model, f=fields)</pre><p>Now,</p><pre>survey = dc.Survey(source_list)<br>simulation = dc.Simulation3DCellCentered(<br>    mesh=mesh, rhoMap=mapping, survey=survey<br>)</pre><pre># compute the fields and predicted data<br>fields = simulation.fields(model)<br>dpred = simulation.dpred(model, f=fields)</pre><h4>Making use of the Data class</h4><p>The purpose of the Data class in SimPEG is to provide a structure which makes it straightforward to grab data associated with a given source and receiver. Essentially, it is a “smart” dictionary. Although we had this implemented in SimPEG previously, we never really used it… and instead, to tell SimPEG about your observed data that you want to use in an inversion, you had to set the dobs property on a survey. This is not obvious, and in a sense, places priority on the wrong thing, the survey, rather than on what our priority is in an inversion: working with our data. So now, the Data class plays an explicit role in setting up an inversion with SimPEG.</p><p>Previously, to construct a data misfit, we would have done something like</p><pre># set the observed data and uncertainties<br>survey.dobs = dobs<br>survey.std = 0.05  # assign 5% relative error<br>survey.eps = 1e-6  # assign a noise floor</pre><pre># create a data misfit<br>dmis = DataMisfit.l2_DataMisfit(survey)</pre><p>The survey carried both the observed data as well as the ability to run simulations and predict data (because we had to do the pesky pair). Now, creating a data misfit looks like:</p><pre># set the observed data and uncertainties<br>data = Data(dobs=dobs, relative_error=0.05, noise_floor=1e-6)</pre><pre># create a data misfit<br>dmis = data_misfit.L2DataMisfit(data=data, simulation=simulation)</pre><p>So we have separated the observed data and associated uncertainties from the simulation, which computes predicted data.</p><h4>No more Python 2.7</h4><p>The 🌎 has <a href="https://python3statement.org/">moved on</a>. Need we say more?</p><p>We recommend python&gt;=3.6 for SimPEG.</p><h4>Documentation Improvements</h4><p>With significant contributions from <a href="https://github.com/dccowan">Devin Cowan</a>, the <a href="http://docs.simpeg.xyz/index.html">SimPEG docs</a> contain many more examples and tutorials! For the geophysical problems we support in SimPEG, there are now tutorials that walk through both setting up and running a forward simulation as well as an inversion. Documentation can always be improved, so please take a look, and share your questions and ideas!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_fv9EWXKqGtptngpe3Sukw.png" /></figure><h4>Renaming of modules</h4><p>We have made efforts to rename many modules, classes and functions with PEP8 style names. Most classes and functions should give you deprecation warnings if you try to use them. However, the modules have all been renamed. For example, SimPEG.EM.Static.DC is now SimPEG.electromagnetics.static.resistivity. We recommend looking at the <a href="http://docs.simpeg.xyz/content/release/0.14.0-notes.html">release notes</a> for a comprehensive overview of the changes and the <a href="http://docs.simpeg.xyz/index.html#simpeg-tuts">tutorials section </a>of the documentation for examples of the updated name-space for each geophysical problem included in SimPEG.</p><h4>Bonus items</h4><p>In addition to the major structural changes that were the initial goal of this release, we have also made some general efficiency improvements, particularly in the <a href="https://www.dropbox.com/s/vvdfjbmwp0a7u2p/open-source-abstract-submission.pdf?dl=0">DC and IP codes</a> motivated by the Geoscientists Without Borders project: <a href="https://medium.com/gwb-myanmar"><em>Improving Water Security in Mon State, Myanmar</em></a>. As part of this we now have a 1D layered Earth simulation and inversion written for SimPEG. We have also provided a toggle for the 2D and 3D DC simulations that should drastically decrease computation time and memory requirements for DC arrays with many overlapping dipole sources, (i.e. a wenner type array common in groundwater applications). Also, the IODC class can now generate a TreeMesh in 2D for you!</p><p>Another new area of active development is incorporating dask to parallelize operations. This is in the experimental stage, but you can toggle the dask implementation on by importing SimPEG.dask prior to other SimPEG imports</p><pre>import SimPEG.dask<br>from SimPEG.electromagnetics import resistivity as dc</pre><p>Finally, of course, we <a href="http://docs.simpeg.xyz/content/release/0.14.0-notes.html#closed-issues">squashed a few bugs</a> 🐛!</p><h4>A note on backwards compatibility</h4><p>We have worked to make many of the changes backwards compatible to ease the transition (a big thanks to <a href="https://github.com/jcapriot">Joe Capriotti</a> 👏 !). <em>Most</em> previously written code should work with only small changes to imports. Warning and error messages will inform you of updates you can make to your code in order to align with the new implementation. Be on the lookout for keyword argument and class property renamings. In the next minor release of SimPEG (0.15), we will be introducing breaking changes that reduce some of this backwards compatibility, so for active projects, we recommend you start migrating your code. For archived projects that are complete (e.g. like those in the <a href="https://github.com/simpeg-research">simpeg-research</a> GitHub organization), we recommend that you pin the version of SimPEG you used to produce those results in your requirements.txt and / or environment.yml file.</p><h3>How to connect</h3><p>The <a href="http://simpeg.discourse.group/">SimPEG discourse</a> is the go-to place for questions, discussions and help on using SimPEG. We have a <a href="https://simpeg.discourse.group/t/simulation-refactor-and-simpeg-0-14/110">dedicated post for the simulation refactor</a>, so feel free to post your questions there as they arise! We also have an <a href="http://slack.simpeg.xyz/">open Slack group</a> for chatting with users, developers and folks who follow the project.</p><p>We hold meetings weekly at 10:30am PDT. If you would like to join us, please join the #meetings channel on slack; this is where we circulate the video link each week. All meetings are <a href="https://www.youtube.com/watch?v=gfqpXEByjr8&amp;list=PLd9tNwsUm9jOagLQEnxdeIPE4L4bx5Ujg&amp;index=119">recorded and available on youtube</a>.</p><h3>Looking ahead</h3><p>We are continuing to work on improving efficiency throughout the codebase as well as parallelizing all SimPEG simulations. A current focus for many on the team is improving our implementation for <a href="https://simpeg.discourse.group/t/natural-source-methods/95">Magnetotellurics and Natural Source EM methods</a>.</p><p>We also have plans to implement a higher-level API for SimPEG in order to streamline the implementation of simulations and inversions. This will include things like utilities for building a simulation mesh based on a given survey geometry, functions for setting up a “vanilla” Tikhonov inverse problem with a beta-cooling schedule, and a command-line-interface to SimPEG.</p><p>There is still lots to be done! And we look forward to continued and growing involvement from the community 🎉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d67d81a654cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simpeg/simpeg-release-of-0-14-d67d81a654cb">SimPEG release of 0.14</a> was originally published in <a href="https://medium.com/simpeg">simpeg</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jupyter meets the Earth]]></title>
            <link>https://medium.com/jupyter-blog/jupyter-meets-the-earth-1b0eb33c83f?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b0eb33c83f</guid>
            <category><![CDATA[geoscience]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 17:48:58 GMT</pubDate>
            <atom:updated>2020-08-07T17:34:55.196Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/388/1*s3i12gpdCYyM0srHQkPZnw.png" /></figure><p><em>By Lindsey Heagy and Fernando Pérez</em></p><p>We are thrilled to announce that the NSF is funding our EarthCube proposal <em>“Jupyter meets the Earth: Enabling discovery in geoscience through interactive computing at scale”</em> (<a href="https://doi.org/10.5281/zenodo.3369938">pdf</a>). The team working on this project consists of Fernando Pérez [1, 2, 3], Joe Hamman [4], Laurel Larsen [5], Kevin Paul [6], Lindsey Heagy [1], Chris Holdgraf [1, 2] and Yuvi Panda [7]. Our project team includes members from the <a href="https://jupyter.org/">Jupyter</a> and <a href="http://pangeo.io/">Pangeo</a> communities, with representation across the geosciences including climate modeling, water resource applications, and geophysics. Three active research projects, one in each domain, will motivate developments in the Jupyter and Pangeo ecosystems. Each of these research applications demonstrates aspects of a research workflow which requires scalable, interactive computational tools.</p><p>In this project we intend to follow the patterns that have made Jupyter an effective and successful platform: we will drive the development of computational machinery by concrete use cases from our own experience and research needs, and then find the appropriate points for extension, abstraction, and generalization. We are motivated to advancing research of contemporary importance in geoscience, and are equally committed to producing work that leads to broad impact, general use infrastructure that benefits scientists, educators, industry, and the general community.</p><p>The adoption of open languages such as Python and the coalescence of communities of practice around open-source tools, is visible in nearly every domain of science. This is a fundamental shift in how science is conducted and shared. In recent years, there have been several high-profile examples in which open tools from the Python and Jupyter ecosystems played an integral role in the research, from data analysis to the dissemination of results. These include the first image of a black hole from the <a href="https://eventhorizontelescope.org/">Event Horizon Telescope team</a> and the detection of gravitational waves by the <a href="https://www.caltech.edu/about/news/gravitational-waves-detected-100-years-after-einstein-s-prediction-49777">LIGO collaboration</a>. The utility of open-source software in projects like these and the success of open communities such as Pangeo, provide evidence of the force-multiplying impact of investing in an ecosystem of open, community-driven tools. Through this project, we will advance this open paradigm in geoscience research, while strengthening and improving the infrastructure that supports it. We made this argument when discussing the intended impacts of our proposal, and we are pleased that the NSF is investing in this vision.</p><h3>Geoscience use cases</h3><p>Given our project’s aims and approach, participating actively in domain research is crucial to our success. The following descriptions are meant to offer a flavour of the research questions we are tackling, each led by a geoscientist in the team.</p><p><strong>CMIP6 climate data analysis (Hamman). </strong>The <a href="https://www.wcrp-climate.org/wgcm-cmip">World Climate Research Program’s Coupled Model Intercomparison Project</a> is now in its sixth phase and is expected to provide the most comprehensive and robust projections of future climate predictions. When complete, the archive is expected to exceed 18 PB in size. In the coming years, this collection of climate model experiments will form the basis for fundamental research, climate adaptation studies, and policy initiatives. While the CMIP6 dataset is likely to hold new answers to many pressing climate questions, the sheer volume of data is likely to present significant challenges to researchers. Indeed, new tools for scalable data analysis, machine learning, and inference are required to make the most out of these data.</p><p><strong>Large-Scale Hydrologic Modeling (Larsen). </strong>Streamflow forecasts are a valuable tool for flood mitigation and water management. Creating these forecasts requires that a variety of data types be brought together including model-generated streamflow estimates, sensor-based observations of water discharge, and hydrometeorological forcing factors, such as precipitation, temperature, relative humidity, and snow-water equivalent. The integration of simulated and observed data over disparate spatial and temporal scales creates new avenues for exploring data science techniques for effective water management.</p><p><strong>Geophysical inversions (Heagy).</strong> Geophysical inversions construct models of the subsurface by combining simulations of the governing physics with optimization techniques. These models are critical tools for locating and managing natural resources, such as groundwater, or for assessing the risk from natural hazards, such as volcanoes. Today, we need models applicable to increasingly complex scenarios, such as the socially delicate task of developing groundwater management policies in water-limited regions. This will require the development of new techniques for combining multiple geophysical data sets in a joint inversion, as well as the use of statistical and data science methods for including geologic and hydrologic data in the construction of 3D models.</p><p>These scientific problems exhibit, each with its own flavour, similar technical challenges with respect to handling large volumes of data, performing expensive computations, and doing both of these as a part of the interactive, exploratory workflow that is necessary for scientific discovery.</p><h3>Jupyter &amp; Pangeo: empowering scientists</h3><p>Jupyter and Pangeo are both open communities that share the goal of developing tools and practices for interactive scientific workflows; these tools aim to deliver practical value to scientists who, in the course of everyday research, face a combination of big data and large-scale computing needs.</p><p><strong>Project Jupyter</strong> creates open-source tools and standards for interactive computing. These span the spectrum from low-level protocols for running code interactively up to <a href="https://blog.jupyter.org/jupyterlab-is-ready-for-users-5a6f039b8906">the web-based JupyterLab interface</a> that a researcher uses. Jupyter is agnostic of programming language: over <a href="https://github.com/jupyter/jupyter/wiki/Jupyter-kernels">130 different Jupyter kernels exist</a>, and they provide support for most programming languages in widespread use today. Jupyter can be run on a laptop, in an HPC center, or in the cloud. Shared-infrastructure deployments (e.g. HPC / cloud) are enabled by JupyterHub, a component in the Jupyter toolbox that supports the deployment and management of Jupyter sessions for multiple users. The development process of tools in the Jupyter ecosystem is community-oriented and includes a diverse set of stakeholders across research, education, and industry. The project has a strong tradition of building tools that are first designed to solve specific problems, and then generalized to other users and applications.</p><p>A <strong>Pangeo Platform</strong> is a modular composition of open, community-driven projects, tailored to the scientific needs of a specific scientific domain. In its simplest form, it is based on the following generic components: a browser-based user interface (<a href="https://jupyter.org/">Jupyter</a>), a data model and analytics toolkit (<a href="http://xarray.pydata.org/">Xarray</a>), a parallel job distribution system (<a href="https://dask.org/">Dask</a>), a resource management system (either <a href="https://kubernetes.dask.org/en/latest/">Kubernetes</a> or a job queuing system such as <a href="https://jobqueue.dask.org/">PBS</a>), and a storage system (either cloud object store or traditional HPC file system). These are complemented by problem- and domain-specific libraries.</p><p>This modular design allows for individual components to be readily exchanged and the system to be applied in new use cases. <a href="https://medium.com/pangeo/announcing-pangeo-earthcube-award-fefbe54acbec">Pangeo was created by, and for, geoscientists</a> faced with large-scale data and computation challenges, but such problems are now common in science. Researchers in a variety of disciplines including neuroscience and astrophysics are working to adapt the Pangeo design pattern for their communities. Beyond the initial Pangeo deployments supported by the NSF EarthCube grant for Pangeo, the platform has been adopted internationally, including by the <a href="https://medium.com/pangeo/whats-so-cool-about-pangeo-974598f4bafc">UK Met office</a>. It has also supported new research and education efforts from other federal agencies, such as NASA’s HackWeek focused on the analysis of <a href="https://medium.com/pangeo/icesat-2-hackweek-mix-70-scientists-and-1-pangeo-jupyterhub-for-5-days-and-what-do-you-get-85f5267a4dfa">ICESat-2 data</a>.</p><h3>User-Centered Development</h3><p>Pushing the boundaries of any toolset unveils areas for improvement and opportunities for developments that streamline and upgrade the user experience. We aim to take a holistic view of the scientific discovery process, from initial data acquisition through computational analysis to the dissemination of findings. Our development efforts will make technological improvements within the Jupyter and Pangeo ecosystems in order to reduce pain-points along the discovery lifecycle and to advance the infrastructure that serves scientists. Following established patterns in Jupyter’s development, we take a user-first, needs-driven approach and then generalize these ideas to work across related fields. Broadly, there are 4 areas along the research lifecycle where we will invest development efforts, which we discuss next.</p><p><strong>Data discovery. </strong>An early step in the research process is locating and acquiring data of interest. Data catalogs provide a way to expose datasets to the community in a way that is structured. Within the geosciences, there are a number of emerging community standards for data catalogs (e.g. THREDDS, STAC). To streamline access to such data sets, we plan to develop JupyterLab extensions which provide a user-interface that exposes these catalogs to researchers. This work will build upon the <a href="https://github.com/jupyterlab/jupyterlab/issues/5548">JupyterLab Data Registry,</a> which will provide a consistent set of standards for how data can be consumed and displayed by extensions in the Jupyter ecosystem, as well as <a href="https://intake.readthedocs.io/en/latest/index.html">Intake</a>, a lightweight library for finding, loading, and sharing data which is already serving the Pangeo community. Our communities are already <a href="https://github.com/jupyterlab/jupyterlab-data-explorer/issues/51">discussing potential avenues for integration</a> between these tools.</p><p><strong>Scientific discovery through interactive computing. </strong>The Jupyter Notebook has been adopted by many scientists because it supports an iterative, exploratory workflow combining code and narrative. Beyond code, text, and images, Jupyter supports the creation of Graphical User Interfaces (GUIs) with minimal programming effort on the part of the scientist. The <a href="https://jupyter.org/widgets">Jupyter widgets framework</a> lets scientists create a “Research GUI” that combines scientific code with interactive elements such as sliders, buttons and menus in just a single line of code, while still allowing for extensive customization and more complex interfaces when required. In this project, we will develop custom widgets tailored at the specific scientific needs of each of our driving use cases.</p><p>Beyond their utility in the exploratory phase of research, interactive interfaces, or “dashboards” provide a mechanism for delivering custom scientific displays to collaborators, stakeholders, and students for whom the details of the code may not be pertinent. <a href="https://blog.jupyter.org/and-voil%C3%A0-f6a2c08a4a93">Voilà</a> is a project, led by the <a href="http://quantstack.net/">QuantStack</a> team, that enables dashboards to be generated from Jupyter notebooks. We plan to develop interactive dashboards using Voilà for our geoscience use-cases, contribute generic improvements to the Voilà codebase, and provide a demonstration of how researchers can deploy dashboards to share their research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*djLNdz13Z4kickGSQFCNUQ.png" /><figcaption><em>Research GUIs to explore Maxwell’s equations in research and education. Photo credit: </em><a href="https://medium.com/u/e8861949d0cf"><em>SEOGI KANG</em></a></figcaption></figure><p><strong>Established tools and data visualization.</strong> Many widely-used tools, particularly for visualization (e.g. Ncview, Paraview), are desktop-based applications and therefore cannot easily be used in cloud or HPC workflows. In some cases, modern, open-source alternatives are available. But often for specialized tasks, modern tools may not yet have functionality equivalent to the desktop version. JupyterHub can readily serve non-Jupyter web-native software applications such as RStudio, Shiny applications, and Stencila to users; under this project we aim to extend JupyterHub to also be able to serve desktop-native applications.</p><p><strong>Using and managing shared computational infrastructure.</strong> JupyterHub makes it possible to manage computing resources, user accounts, and provide access to computational environments online. Currently, JupyterHubs in the Pangeo project are deployed and maintained using the <a href="http://z2jh.jupyter.org/en/latest/">Zero to JupyterHub guide</a> alongside the <a href="https://hubploy.readthedocs.io/en/latest/">HubPloy library</a>. Together, these libraries have simplified the initial setup and automated upgrades to the Hubs. There are still many improvements that can make JupyterHub more suitable for larger, more complex deployments, both in terms of managing users and efficiently allocating resources. Under this project, we plan to build tools which collect metrics such as CPU and memory usage and expose these to both users and administrators so they can make more efficient use of the Hub. For shared deployments, we will improve user management so that user-groups can be used to manage permissions and allocations, and so that usage can be tracked and appropriately billed to the relevant grants. Within the HubPloy library, we also plan to make improvements to streamline continuous deployments so that installation and upgrade processes are repeatable and reliable.</p><h3>An opportunity for meaningful impact — join us!</h3><p>The impacts of climate change and the need for data-driven management of resources are some of the most critical and complex challenges facing society today. In recent years, we have experienced severe droughts in California and are in the midst of water management crises in the Central Valley, while devastating wildfires have destroyed entire communities. Through this partnership between researchers and Jupyter developers, we hope to contribute to the advancement of science-based solutions to these challenges, both by contributing directly to the research and by improving the open ecosystem of tools available to researchers and the stakeholders impacted by these issues.</p><p>If developing open-source tech to advance research in geoscience and beyond excites you, then please <a href="/service/mailto:lheagy@berkeley.edu;fernando.perez@berkeley.edu">get in touch</a>! At UC Berkeley, we will be hiring in 2 positions: a dev-ops position focussed on JupyterHub and shared infrastructure deployments, and a JupyterLab-oriented role focussed on extensions, dashboards, and interactivity. There will also be a position opening up at NCAR for a software engineer targeting improvements to improving the user experience of Xarray and Dask workflows.</p><p>Even if you aren’t looking for a new job, there are other ways to get involved with both the Jupyter and Pangeo communities. We welcome new participants to the <a href="https://pangeo.io/meeting-notes.html">weekly Pangeo meetings</a> (on Wednesdays alternating between 4p GMT and 8p GMT) and there are <a href="https://discourse.jupyter.org/t/jupyter-community-calls/668">monthly Jupyter community calls</a>, which are open and meant to be accessible to a wide audience. Outside of calls, general Jupyter conversations happen on the <a href="https://discourse.jupyter.org/">Jupyter discourse</a> and Pangeo conversations are typically on the <a href="https://github.com/pangeo-data/pangeo">Pangeo GitHub</a>.</p><h3>In closing: a step toward sustainable open science</h3><p>This project provides our team with $2 Million in funding over 3 years as a part of the NSF <a href="https://earthcube.org/">EarthCube</a> program. It also represents the first time federal funding is being allocated for the development of core Jupyter infrastructure.</p><p>The open source ecosystem that Jupyter and Pangeo belong to has become part of the backbone that supports much of today’s computation in science, from astronomy and cosmology to microbiology and subatomic physics. Such broad usage represents a victory for this open and collaborative model of building scientific tools. Much of this success has come through the efforts of scientists and engineers who are committed to an open model of science, but who have had to work with little direct funding, minimal institutional support, and few viable career paths within science.</p><p>There is real strategic risk to continuing with the implicit assumption that scientific open-source tools can be developed and maintained “for free.” If open, community-driven tools are to sustainably grow into the computational backbone of science, we need to recognize this role and support those who create them as regular members of the scientific community (we recently talked about this in more detail in a <a href="http://www.tvworldwide.com/events/nsf/190815">talk at NSF headquarters</a>). Projects like ours, where funding and resources are explicitly allocated toward this goal, are a step in the right direction. We hope that our experiences will contribute to ongoing conversations in the scientific community around these complex issues.</p><p>In the past, we have tried to maintain a close relationship between domain problems and software development in Jupyter. However, this has typically been done in an ad-hoc manner, either by “hiding” the software development under the cover of science or by having funding to Jupyter alone. This is the first project where we explicitly partner with a team of domain scientists to simultaneously drive forward domain research and the development of Jupyter infrastructure.</p><p>We are excited about this opportunity and hope to be able to demonstrate that investing in open tools can be a force-multiplier of resources. As always, our work will be done openly, transparently, and with constant community engagement. We look forward to your critiques, ideas, and contributions to make this effort as successful as possible.</p><h3>Acknowledgments</h3><p>Thanks to Joe Hamman, Chris Holdgraf, and Doug Oldenburg for constructive feedback and edits on this blog post.</p><p>Many thanks to <a href="https://www.ldeo.columbia.edu/user/rpa">Ryan Abernathey (Columbia)</a>, <a href="https://www.usgs.gov/staff-profiles/paul-a-bedrosian?qt-staff_profile_science_products=3#qt-staff_profile_science_products">Paul Bedrosian (USGS)</a>, <a href="https://quantstack.net/sylvain.html">Sylvain Corlay (QuantStack)</a>, <a href="https://www.usgs.gov/staff-profiles/richard-p-signell?qt-staff_profile_science_products=0#qt-staff_profile_science_products">Rich Signell (USGS)</a>, and <a href="https://www.nersc.gov/about/nersc-staff/data-analytics-services/rollin-thomas/">Rollin Thomas (NERSC)</a>, who provided us with letters of support for this project; we look forward to working with you all! We are also grateful to <a href="https://www.nsf.gov/staff/staff_bio.jsp?lan=sumishra">Shree Mishra</a>, our NSF Program Director on this project, and to Dave Stuart for their support as we move forward with the project. This project is a part of the to the EarthCube program and we look forward to engaging with its working group.</p><p>Finally, the sustained growth of Jupyter to the large-scale project that it has become would not have happened without the generous support of the Alfred P. Sloan, the Gordon and Betty Moore, and the Helmsley Foundations, as well as the leadership of Josh Greenberg and Chris Mentzel respectively at Sloan and Moore.</p><p>This work is supported by the NSF EarthCube program under awards 1928406, 1928374</p><p><strong>Affiliations</strong></p><p>[1] UC Berkeley, Statistics Department</p><p>[2] UC Berkeley, Berkeley Institute for Data Science</p><p>[3] Lawrence Berkeley National Lab, Computational Research Division</p><p>[4] National Center for Atmospheric Research, Climate and Global Dynamics Laboratory</p><p>[5] UC Berkeley, Department of Geography</p><p>[6] National Center for Atmospheric Research, Computational Information Systems Laboratory</p><p>[7] UC Berkeley, Division of Data Sciences</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b0eb33c83f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jupyter-blog/jupyter-meets-the-earth-1b0eb33c83f">Jupyter meets the Earth</a> was originally published in <a href="https://medium.com/jupyter-blog">Jupyter Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Team meeting in Montreal]]></title>
            <link>https://medium.com/simpeg/team-meeting-in-montreal-aad61ecdea8d?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/aad61ecdea8d</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[geophysics]]></category>
            <category><![CDATA[open-source-software]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Mon, 22 Jul 2019 21:11:59 GMT</pubDate>
            <atom:updated>2020-02-20T06:02:20.609Z</atom:updated>
            <content:encoded><![CDATA[<p><em>July 17, 2019</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sGnhtEi9qC3HmcO8_UxM5g.jpeg" /><figcaption>SimPEG team in Montreal!</figcaption></figure><p>Last week, the <a href="http://iugg2019montreal.com/">International Union of Geodesy and Geophysics</a> conference was held in Montreal and the SimPEG team took the opportunity to hold a 1-day meeting for those of us attending. Six of us (<a href="https://github.com/fourndo">Dom Fournier</a>, <a href="https://github.com/dougoldenburg">Doug Oldenburg</a>, <a href="https://github.com/jcapriot">Joe Capriotti</a>, <a href="https://github.com/sgkang">Seogi Kang</a>, <a href="https://github.com/thast">Thibaut Astic</a> and <a href="https://github.com/lheagy">myself</a>) got together to discuss a roadmap for working towards SimPEG 1.0! We broadly covered 4 topics:</p><ul><li><strong>Simulation refactor: </strong>Refactoring the Problem and Survey classes in SimPEG to a Simulation class and a lighter-weight Survey class</li><li><strong>Sources and receivers: </strong>Thinking through the structure of the source and receiver classes to reduce redundancy of the storage of projection matrices and improve integration between the natural source and frequency domain electromagnetic codes</li><li><strong>Parallelization and efficiency: </strong>parallelizing the inversion using decomposition approaches, parallelizing forward simulations, identifying places to contribute to the scientific python stack</li><li><strong>Goals for SimPEG 1.0: </strong>development items, refactoring, and community practices to take SimPEG to a 1.0 release 🚀</li></ul><h3>Simulation Refactor</h3><p>The first topic of the day was about the ongoing simulation-refactor within SimPEG (under construction here: <a href="https://github.com/simpeg/simpeg/pull/786">#786</a>, original issue here: <a href="https://github.com/simpeg/simpeg/issues/562">#562</a>). In a nutshell, the structure of the current Problem and Survey classes is challenging to explain, does not easily allow other forward modelling codes to be plugged in to SimPEG, and can not be serialized, meaning it is not easy to parallelize the current codes. These symptoms indicate that we need to re-think the structure.</p><h4>The highlights…</h4><p>The new Survey will be much more lightweight. As before, it will contain a source_list , where each source has a receiver_list of receivers that are listening to it (but now with PEP8 names!), and some utilities, for example the ability to fetch sources by frequency. The Survey previously had the dpred method, meaning it would compute data. This is no longer the case, the Simulation will now do all of the heavy lifting here. The Survey also used to keep track of dobs (the observed data), as well as data uncertainties. This will now be handled by the Data class, which will take a survey as an input and treat it as a property of the data. Similarly, a survey will be an input to the Simulation class to provide the information, rather than having to pair them (this was a source of problems for serializing the class).</p><p>This also propagates changes to the data_misfit module. Previously, a data misfit would have been instantiated with only a survey (which both stored dobs and could compute dpred ), now, the data misfit will be instantiated with data and a simulation. For example, in the current framework, to set up a data-misfit term for a frequency domain electromagnetic simulation, it would look something like…</p><pre># set up a simulation<br>survey = FDEM.Survey(source_list)<br>problem = FDEM.Problem3D_e(mesh, sigmaMap=mapping)<br>problem.pair(survey)</pre><pre># compute predicted data<br>dobs = survey.dpred(model)</pre><pre># set the data and uncertainties<br>survey.dobs = dobs<br>survey.std = 0.05</pre><pre># create a data misfit<br>dmis = DataMisfit.l2_DataMisfit(survey)</pre><p>and now…</p><pre># set up a simulation <br>survey = fdem.Survey(source_list)<br>simulation = fdem.Simulation3DE(<br>    mesh, sigma_map=mapping, survey=survey<br>)</pre><pre># compute predicted data<br>dobs = simulation.dpred(model)</pre><pre># set the data and uncertainties<br>data = Data(dobs=dobs, standard_deviation=0.05)</pre><pre># create a data misfit<br>dmis = data_misfit.L2DataMisfit(data=data, simulation=simulation)</pre><h4>Interfacing to other simulations</h4><p>This should simplify our ability to interface to other forward simulation packages (e.g. <a href="https://github.com/empymod/empymod">empymod</a>!). In order to interface to SimPEG to invert data using your forward simulation, you just need a light-weight wrapper class that includes:</p><ul><li>dpred : a method for computing predicted data</li><li>Jvec : a method for multiplying the sensitivity times a vector</li><li>Jtvec : a method for multiplying the adjoint-sensitivity by a vector</li></ul><p>Note that the sensitivity calculations could be derived or estimated using a finite difference approach. Watch for an example with empymod in the near future!</p><h4>The updated framework</h4><p>On the board, we sketched out what the updated framework looks like with the simulation-refactor (the right half of the image) . A couple things to note:</p><ul><li>data is now explicitly included in the framework</li><li>data_misfit now takes a simulation and a data object</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H6GWlfxtO-diWVgQvb9_1Q.png" /></figure><p>We also spent some time talking about how we might remove the InverseProblem class and simply provide a statement of the objective function to the Inversion directly (this is the diagram on the left). This would be a separate pull request from the simulation but is on the roadmap for SimPEG 1.0!</p><h3>Survey Class: Sources and Receivers</h3><p>We topped up our coffees and moved on to the next discussion: the structure of sources and receivers. In particular, we are running into issues of duplication of information. For example, right now in a frequency domain EM simulation, if you want to measure real and imaginary components of the x-oriented magnetic field (<strong>bx</strong>), then both the real and the imaginary component would be different receivers, let’s call them bxr and bxi.</p><pre>bxr = FDEM.Rx.Point_b(locs, orientation=&#39;x&#39;, component=&#39;re&#39;)<br>bxi = FDEM.Rx.Point_b(locs, orientation=&#39;x&#39;, component=&#39;im&#39;)</pre><p>What currently happens is that each of bxr and bxi creates and stores its own projection matrix which interpolates the magnetic flux computed on the simulation grid to the receiver locations. If bxr and bxi are at the same locations, then we have duplicated our efforts. This can start to become costly…</p><p>Similarly, for the integral-equation potential fields codes, the system matrix is constructed based on the unique receiver locations, so we need the ability to easily fetch all of the unique receiver locations (without trying to do a step where we compare numpy arrays of floats!)</p><h4><strong>Sketch of the base receiver classes</strong></h4><p>If instead of each receiver having only a single component, what if we considered an instance of a receiver to be a class to be something that shares a single projection matrix, so</p><pre>bx = fdem.receiver.PointB(<br>    locs, orientation=&#39;x&#39;, components=[&#39;re&#39;, &#39;im&#39;]<br>)</pre><p>To compute these data, we need a projection matrix that interpolates from x-faces of the mesh to the locations (locs), and the same matrix can be used for the real and imaginary components. More complex data, for magnetic flux at an arbitrary orientation could be though of as a composite receiver which contains bx , by , bz receivers. Each of those can interpolate values from the x, y, and z grids, respectively, and then the composite receiver sums them up with the appropriate weights based on the orientation of the receiver.</p><p>A similar thought process can be thought of for DC resistivity. For 3D surveys that are being conducted by companies such as Dias, an array of pole receivers are laid out and then dipole are made by defining pairs of electrodes from this set and subtracting the measured pole-values. This means that we can construct a single projection matrix to go from cell-centers (or nodes depending on the discretization) which gives us the pole measurements and then simply track which values need to be subtracted from each other to create the dipole data. The whiteboard sketch below gives an idea of how a Dipole receiver would be implemented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B_Zz_u9vxlRiTJIt.jpg" /></figure><p>To make the extension to magnetotelluric data, we can again use the idea of a composite receiver, but instead of just listening to a single field (e.g. magnetic flux b), the transfer function receiver would take multiple fields (electric and magnetic) and compute the appropriate impedances.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ncRbqJv5uXHPDcyv84ftzQ.png" /></figure><p>In order to improve the integration between the frequency domain EM codes and the natural source EM codes, we can think about adapting the idea of composite receivers instead to sources so that a plane-wave source is simply a list of two plane-wave sources with orthogonal directions.</p><p>To simplify things for the user, we will need to have a utility or higher-level API, but this gives the general idea at the base. Watch for issues on SimPEG that flesh out these ideas more soon!</p><h3>Scaling SimPEG: Parallelization and Efficiency</h3><p>After breaking for lunch, we came back and started discussion on parallelization and efficiency improvements we can make within SimPEG. With respect to parallelization, there are two avenues we will work on pursuing: (1) parallelization at the level of the objective function, (2) parallelization within a forward simulation. For (1), this is appropriate for mesh-decomposition approaches, such as that being pursued by Dom in the potential fields codes. The inversion model lives on a global mesh, and the forward simulation is broken up into multiple forward simulations, so that only one region of the mesh is refined and the rest is coarsened for each sub-problem. These simulations are run independently, and each has its own data associated misfit term, so the parallelization occurs at the level of the objective function. A similar approach is highly appropriate for airborne time-domain electromagnetics. For (2), problems like frequency domain electromagnetics are embarrassingly parallel, so we just just need to implement it! We will use magnetics and magnetotellurics as our use-cases for driving the initial implementation with dask.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7Ua3WjbRkMBinVnv.jpg" /></figure><p>In particular for the mesh decomposition approaches, there will be lots of details to sort out with respect to how to best optimize mesh sizes, and how to appropriately chunk and store sensitivities in the integral-equation implementations for gravity and magnetics. If you get excited about these problems — get in touch!</p><p>We also discussed some general areas for efficiency improvements, including experimenting with different solvers and identifying areas lower in the scientific python stack where we might be able to contribute improvements. Benchmarking and profiling are on the radar, but these will be performed once we have completed the major refactors within SimPEG.</p><h3>SimPEG 1.0 Goals</h3><p>The final topic of the day was to outline a roadmap for SimPEG 1.0. We discussed technical aspects including: the simulation refactor discussed above, <a href="https://python3statement.org/">removing support for 2.7!</a>, general housekeeping (utils need some 💚), serialization of inversion components (optimization, inversion and directives), and importing simpeg rather than SimPEG.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6iYSgAKshAyHdU2mrkySNA.png" /></figure><p>We also discussed modes of interacting with SimPEG. Right now, we collaborate with many users by providing scripts which drive the simulation or inversion, and input variables are provided in an input file by the user (having an input file to a simulation or an inversion is the common mode of operation for most inversion-code users). The challenge is, that any time we upgrade the code, the script generally needs to be updated. Thus, there is a need to formalize this process a bit. This led us to discuss the idea of “wrappers” or “drivers” which are a higher-level API that provide sensible defaults for many of the forward simulations and inversions (e.g. generate a mesh based on the survey, set defaults for the weights in the regularization, …). It would also be nice if there were a command-line interface to SimPEG, e.g.</p><pre>&gt; simpeg simulate my_grav_simulation.yml<br>&gt; simpeg invert my_grav_inversion.yml</pre><p>Another topic of discussion is how best to interface to the community, provide support, answer questions and communicate updates. Right now, slack and google-groups are our main mode of operation. The plan is to stick with slack for development conversations and try using discourse (e.g. see the <a href="https://discourse.jupyter.org/">Jupyter discourse</a>) for community conversations, questions etc. We would appreciate any feedback you have on how you would like to engage with members of the SimPEG community!</p><p>In the coming weeks, we will be pushing forward on the simulation refactor and summarizing many of our discussion points in issues on the <a href="https://github.com/simpeg/simpeg">SimPEG repository</a>. Watch for new issues, a milestone, and join the development — there is lots to do ⚒!</p><h3><strong>Thanks!</strong></h3><p>Thanks to <a href="https://gif.eos.ubc.ca/about">UBC Geophysical Inversion Facility</a>, the <a href="https://cgem.mines.edu/">Center Gravity, Electrical &amp; Magnetic Studies (CGEM) at Colorado School of Mines</a>, <a href="https://enviro.stanford.edu/">Environmental Geophysics at Stanford</a>, and Fernando Pérez’s lab at UC Berkeley for travel and conference funding.</p><p>Thanks to <a href="https://plot.ly/">Plotly</a> (<a href="http://twitter.com/plotlygraphs">@plotlygraphs</a>) for helping arrange a beautiful conference room space for us at the <a href="https://anomaly-mtl.com/">Anomaly</a> co-working space in Montreal!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aad61ecdea8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simpeg/team-meeting-in-montreal-aad61ecdea8d">Team meeting in Montreal</a> was originally published in <a href="https://medium.com/simpeg">simpeg</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Santiago]]></title>
            <link>https://medium.com/disc2017/santiago-34349c144b20?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/34349c144b20</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[geoscience]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[geophysics]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Sat, 03 Nov 2018 00:02:05 GMT</pubDate>
            <atom:updated>2018-11-03T00:02:05.209Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b8Gj3EXREvuEHq7aCtnAXw.png" /></figure><p><em>Nov 16–17</em></p><p>Following DISC Lab day in <a href="https://medium.com/disc2017/buenos-aires-a93714b4a4bd">Buenos Aires</a>, we hopped on a plane and landed in Santiago, Chile late on Tuesday night. By the time we arrived at our airbnb in the heart of Santiago, it was Wednesday. It was a bit eerie arriving so late in an unfamiliar city, seeing stray dogs running around, and not being entirely sure where our accommodation was. However, when we woke up the next morning, we looked out the window, saw the view captured in the above image, and were please to be situated in a bustling part of the city.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P81vPYE2KIAqtxj5XnaViQ.png" /><figcaption>coffee with Daniel</figcaption></figure><p>On Wednesday afternoon, we met up with Daniel Diaz, our local host to see the venue at the University of Chile and chat about the local applications of interest. Mining is perhaps the most prevalent industry application; one of the case histories we planned to present, <a href="https://storage.googleapis.com/simpeg/disc2017/santiago/5_EM_natural_sources.pdf">Santa Cecilia</a>, incorporates 4 types of electrical and electromagnetic data sets (DC, IP, CSAMT and MT) to characterize a porphyry deposit in Chile. This case history was first presented in <a href="https://medium.com/disc2017/toronto-adb37e7a1054">Toronto</a>, and we were excited to include it for to the home-crowd.</p><p>On the academic side, there is much work being done to understand volcanism in Chile. One of the projects Daniel is involved in is an MT survey over Laguna del Maule, a region of volcanic activity in Chile that is uplifting at a rate of ~25 cm/year!</p><p>We wrapped up our chat getting a few tips from Daniel on what to do for our couple free days after the course.</p><h3>Day 1: DISC Course</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oOJDm6iWWZYzeIRgbsi-4A.png" /><figcaption>Participants at the DISC in Santiago (left &amp; right), Doug using the DC resistivity app to show where the charges are in a DC survey for a tunnel (centre)</figcaption></figure><p>The course started at 9am, and nearly 40 participants attended, among them included some well-informed professionals in the mining industry. Having well-informed participants engage in the course elevates it for everyone (including us!); discussions promote looking at a concept from multiple angles, and new applications or challenges are brought to light when people are willing to share their experiences. In <a href="https://medium.com/disc2017/adelaide-e1a447f12c3e">Adelaide</a>, we encountered this as participants who were involved with data collection and interpretation at Mt Isa (the case history we use to book-end the course) shared some of the current unanswered questions about the site. Here in Santiago, Héctor Verdejo shared aspects of the state of the art for processing DC resistivity and IP data (more coming in the DISC Lab section of the blog). We are grateful to Daniel for his efforts to promote attendance and to Mike Webb and Terry Ritchie for bringing participants from BHP and GRS. Having leaders within a company support initiatives like the DISC makes a significant impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R-RY9fG6SDhFyfskhvob9A.png" /><figcaption>participant of DISC 2017 in Chile</figcaption></figure><p>We have ~21 case histories (and some tutorial material on advanced topics such as EM decoupling) prepared for the presentation. Depending on audience interest in each of the applications or methods, we choose a subset of these at each location. For Santiago, we presented a significant number of these. We reached the end of Natural Sources as we wrapped up day 1, and planned to cover the remaining material on day 2.</p><h3>Day 2: DISC Lab</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCI9hehpgJXnkP218UAuNQ.png" /><figcaption>Day 2: DISC Lab</figcaption></figure><p>We picked up on day 2 with <a href="https://storage.googleapis.com/simpeg/disc2017/santiago/6_GPR.pdf">Ground Penetrating Radar</a>, <a href="https://storage.googleapis.com/simpeg/disc2017/santiago/7_Induced_polarization.pdf">Induced Polarization</a> and finished the “course” portion of the DISC with a <a href="https://storage.googleapis.com/simpeg/disc2017/santiago/8_future.pdf">summary and discussion of the future</a>. From there, we turned the floor over to the participants to discuss the applications they are currently working on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xH53StgSHHfRAeWHNfkkNA.png" /><figcaption>Héctor Verdejo</figcaption></figure><p><strong>Héctor Verdejo </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/santiago/disc_lab/GRS_Disc2017_Stgo.pdf">slides</a>) — There is often a big difference between simulated, theoretical data and measurements taken in the field. Hector, who works for <a href="http://consultgrs.com.au/">GRS</a>, showed an example of DC/IP data collected in a routine survey. The data were contaminated with telluric noise which had to be removed before standard processing techniques could be applied. Magnetotelluric transfer functions were used to estimate the telluric noise which was subsequently subtracted from the data. There are often many types of noise that need to be accounted for to obtain high quality data suitable for inversion. Delineating those noise types and providing software and tutorials to show how the observations can be cleaned up is a long term goal for us. We are pleased that Hector has volunteered to show us how his processing works and we look forward to developing a tutorial about this.</p><p>In the second part of his talk, Hector showed an example of the use of their telluric cancellation at Olympic Dam where both MT and CSEM data were collected. The orebody shows up as a conductive and chargeable target. However, EM coupling can affect the chargeability data and this invites further investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1OdvPL_suWNehzM2_7_7eA.png" /><figcaption>Eduardo Alarcón Guerra</figcaption></figure><p><strong>Eduardo Alarcón </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/santiago/disc_lab/ERT%20Monitoring.pdf">slides</a>) — The concept of capturing surface water in containment ponds and having that recharge an underlying aquifer is something that is being worked on at many locations. Eduardo, who works for Aguaex, is involved in carrying out a time-lapse DC resistivity survey to image subsurface flow when water is injected at the surface. Some of the field challenges were that there were multiple locations at which water was injected and multiple lines of data needed to be acquired rapidly. Preliminary analysis identified locations where water permeated more rapidly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l427e8xFjQEkVLUiFEIW2w.png" /><figcaption>Daniel Díaz</figcaption></figure><p><strong>Daniel Díaz</strong> (<a href="https://storage.googleapis.com/simpeg/disc2017/santiago/disc_lab/cursoEM_DD.pdf">slides</a>) — Chile has considerable geothermal potential, particularly in the northern part where it shares a border with Bolivia and Argentina. Daniel, a professor a Universidad de Chile, has been carrying out Magnetotelluric (MT) surveys in that area for many years. Investigating geothermal areas and also the volcanoes themselves to get an understanding of their composition and dynamics are interesting and important problems and Daniel has a number of students working on projects. The remoteness of the region and the ruggedness of the topography (elevation changes of 2km over a 15 km transect, make acquisition difficult and station spacing is sparse. He presented the results from two areas. The first is an area where Chile’s first geothermal plant has just started. The inversion of the MT data was challenging because of the effects of topography and the size of the model. Nevertheless, first results were obtained along with a geologic interpretation.</p><p>The second area is the El Tatio geyser field in northern Chile. Of special interest was a large dacite dome which was only about 20,000 years old. MT data have been collected and preliminary inversions have been obtained. The MT data will be complemented by the acquisition of Time domain EM data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hwMS5mWoPu-kunCEVlL8Qw.png" /><figcaption>David Maldonado</figcaption></figure><p><strong>David Maldonado </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/santiago/disc_lab/Prensentacion_1.pdf">slides</a>) — Magnetic data are modelled with Maxwell’s equations at zero frequency and so a talk about inverting total field data to find a 3D model of magnetization fits within our EM framework. David presented a synopsis of his approach to solve this problem.</p><p>We concluded day 2 by showing the resources available within <a href="http://geosci.xyz/">GeoSci.xyz</a>, the numerical tools in <a href="http://simpeg.xyz/">SimPEG</a>, and tutorials, including <a href="https://library.seg.org/doi/abs/10.1190/tle36080696.1">a tutorial on Magnetotellurics</a>, for getting up and running with the software.</p><h3>From the participants</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tQY9My-Kagp1TxVXwOiE8A.png" /><figcaption>coffee breaks (with delicious fruit skewers!)</figcaption></figure><p><em>“It was a great short course, with very good slides and supporting material [that took] into consideration several methods and applications. This is an exercise that has to repeat many times, especially in South America. I would like in the future if the SEG could do this same source format with inversion [of] geophysical data, use of the full waveform, and numerical modelling.” — </em>Eduardo Alarcon, Geological Engineer</p><p><em>“The content of [the] course was very clear and illustrative. I like the simulations using SimPEG. I believe this [is] a good tool [for] modelling and better understanding some aspects of EM surveys” — </em>Halis Benítez</p><p><em>“This course exceeded my expectations, and mine were very, very high! It meant a lot to me to get inspiration in the work we do everyday. You saved me! Thank you for all your effort and hard work in putting this together. I appreciate your approachability and kindness in addressing the lectures.” </em>— Valentina Olmos Salvo, Geophysicist</p><p><em>“Long live the fundamentals! The course completely fulfilled my expectations. It was a great time to view concepts and understand those in a different or better way.” </em>— Hector Verdeso, Geophysicist at GRS</p><p><em>“Really awesome. I could understand things I never could before. I loved how you showed [concepts] by images and videos [of] how the currents and magnetic fields are.” </em>— Daniela Montecinos</p><p><em>“Very good, organized, well paced, appropriate level of detail. Great guidance towards other resources. Great interaction with the audience. Comfortable atmosphere.” — </em>Brendan Purchase, Geophysicist</p><p><em>“Doug’s presentations were excellent, good exploration of complex ideas by breaking into simple terms and visualizations. Valuable refresher course for EM fundamentals.” — </em>Andy Roberts, Geophysicist, Barrick</p><p><em>“Overall [it] was a great course, very well structured, that goes from the basics, through the concepts, moving from time domain to frequency domain, thinking logically about the physical processes occurring and taking it to the case studies where all the concepts get “proved.” </em>— Camila Leyton Azocat</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNaczbgjEbjiL_xL44bk8w.jpeg" /><figcaption>Participants in Chile</figcaption></figure><h3>A few adventures</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ip3fPaXPqlaCrv1eBjfUnQ.png" /><figcaption>Sampling street food in Santiago.</figcaption></figure><p>Sampling street food has got to be one of the best way to get to know a city; Santiago did not disappoint! On our first evening in Santiago — the day before the DISC — we walked the streets near out accommodation and sampled burritos and an empanada for dinner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBtvBEr9rFzBws40Gzobow.png" /><figcaption>Parque Forestal, National Museum of fine arts, display inside the museum</figcaption></figure><p>Following the DISC, we had 2 free days in Santiago. On our first day, we did a self-guided walking tour. We started off wandering along Parque Forestal, a picturesque urban park, towards the National Museum of Fine Arts. We stopped in at the museum and took in a range of displays from historic statues to modern, interactive displays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WAGG6ar3mK1rS7KAHBqjkg.png" /><figcaption>La Vega Central market</figcaption></figure><p>From the museum, we walked to the La Vega Central fresh food market. The many rows of stalls were stocked with fresh peppers, large squash, and local fruit, including plenty of nisperos, a bright orange fruit native to Chile that is similar in shape and colour to an apricot. Seeing all of the fresh produce helped us build up an appetite, so we grabbed a pork arepa and a chicken taco for lunch in the market. Lunch was accomanied by a papelon &amp; limon — a refreshing lemonade-style drink.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mvewtC8f3TsdlvXGK8Za7w.png" /><figcaption>Cerro Santa Lucia</figcaption></figure><p>After lunch, walked through the central market, a large fish market and then made our way to Cerro Santa Lucia, an iconic hill in the centre of Santiago. The hill is lined with gardens, fountains, beautiful paths and viewpoints of the city. Charles Darwin visited the park in 1833 and was taken by its beauty — a plaque with his signature commemorates the occasion and one of the gardens has been named after him. We spent most of the afternoon walking around the parks and met a young group of scouts who were out for the day taking photos. We stopped for dinner at a nearby restaurant where we watched some street performers before making our way back to the airbnb.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A3goFAkejmriDobrkZPhBA.png" /><figcaption>Saturday evening in Santiago</figcaption></figure><p>As we walked back, we heard a violin fill the air. We encountered the performer and stopped to listen (conveniently, there was popcorn being sold nearby!). With that, our day was complete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4VAiSJbXjkafwI7IsTeH-g.png" /><figcaption>9 different fruits for breakfast!</figcaption></figure><p>Each morning in Santiago, we started off with a delicious spread of fruit for breakfast. Having been to the markets the day before, we had a quite the variety! Among them were a number of local fruits including: mangosteen, chirimoya, and nispero.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgsav-AEfjJMkI-dDpuqAQ.png" /><figcaption>hike up San Cristobal</figcaption></figure><p>Our plan for the day was to hike up San Cristobal. It is famous for the statue of the Virgin on top, and was a viewpoint from our airbnb. It was close enough that we could walk to the base. The walk to the base took us through the Bellavista neighbourhood — a colourful neighbourhood lined with dramatic graffiti.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZaeLXi5NiASywn15T9NidA.png" /><figcaption>mote con huesillo</figcaption></figure><p>We started the hike late-morning and took our time (it was a hot day!). As a break along the way, we stopped at the half-way point for a mote con huesillo, a summertime drink / snack that combines dried peaches, a sweet tea, and cooked wheat. It was a popular stop with lots of families enjoying their Sunday afternoon together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k-2QaxHSrQINLkd-nzr4gA.png" /><figcaption>views and photos from the top of San Cristobal</figcaption></figure><p>We continued along to the top and were fortunate to have a clear day to take in the vistas of Santiago.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mjPq_vaTYtvY-Seu20uX_A.png" /><figcaption>view of Santiago from San Cristobal</figcaption></figure><p>Sunday was election day in Chile, so many of the restaurants were closed, but we were fortunate to find a seafood place in the Bellavista area. We had ceviche and grilled fish for dinner before heading back to our airbnb to get packed and ready for our early flight out the Bolivia the next morning.</p><h3>Thank you</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KhApk8lXJg0SOPN7HAF0JA.png" /><figcaption>Daniel Diaz and Doug Oldenburg</figcaption></figure><p>Daniel Diaz and Diana Comte were very proactive hosts and helped draw a strong group of participants in Chile — we thank them both for their efforts as well as the Advanced Mining Technology Center (AMTC) and the Geophysics Department (FCFM) for hosting us!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34349c144b20" width="1" height="1" alt=""><hr><p><a href="https://medium.com/disc2017/santiago-34349c144b20">Santiago</a> was originally published in <a href="https://medium.com/disc2017">DISC 2017</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[July 30 — Aug 5]]></title>
            <link>https://medium.com/simpeg/july-30-aug-5-19a65e63cd79?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/19a65e63cd79</guid>
            <category><![CDATA[geophysics]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[volcano]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[open-science]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Tue, 07 Aug 2018 03:19:23 GMT</pubDate>
            <atom:updated>2018-08-07T03:19:23.515Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This week in SimPEG…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*EvwVv2-3K3gprB-DY3dA8Q.png" /></figure><p><strong>Craig Miller</strong>, Seogi Kang and Dom Fournier had their paper: <a href="https://agupubs.onlinelibrary.wiley.com/doi/abs/10.1029/2018GL078780"><em>Distribution of vapour and condensate in a hydrothermal system: Insights from self-potential inversion at Mount Tongariro, New Zealand</em></a><em>, </em>accepted this week!</p><p>Volcanologists routinely sample fluids from springs and vents on volcanoes to determine that volcano’s state of unrest. Prior to the 2012 Te Maari eruptions at Mt Tongariro, New Zealand, changes in water and gas chemistry that preceded the eruption, were found at only a few of the vents and springs sampled, despite evidence for a large hydrothermal system, thought to connect them. We wanted to understand why chemical changes in the water and gas weren’t observed more widely on the volcano, and if it was related to the pattern of underground water movement. Water moving within a rock generates a small electrical charge, measurable on the surface as a voltage. We mapped voltage variations around the hydrothermal system at Mt Tongariro, and developed new 3D computer software to simulate the subsurface water movement. We found varying degrees of water and steam within the hydrothermal system that is likely controlled by the rock’s ability to allow water movement. Importantly, we found no connectivity between individual springs and vents on the volcano, explaining observations of geographically isolated changes in water and gas chemistry prior to the eruptions. This has important implications for how geochemical monitoring of similar multivent volcanoes is undertaken.</p><p>Notebooks used to generate the results are available at: <a href="https://github.com/simpeg-research/miller2018_Tongariro_SP_inversion">https://github.com/simpeg-research/miller2018_Tongariro_SP_inversion</a>.</p><h3>At the meeting last week…</h3><p>Dom Fournier led the meeting on OcTree meshes and utilities for generating meshes.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FylCF8uR-tME%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DylCF8uR-tME&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FylCF8uR-tME%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6b09afbde443e755d8800161c6b253c4/href">https://medium.com/media/6b09afbde443e755d8800161c6b253c4/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19a65e63cd79" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simpeg/july-30-aug-5-19a65e63cd79">July 30 — Aug 5</a> was originally published in <a href="https://medium.com/simpeg">simpeg</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[July 23–29]]></title>
            <link>https://medium.com/simpeg/july-23-29-11bd0de6464c?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/11bd0de6464c</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[geophysics]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[geoscience]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 05:12:46 GMT</pubDate>
            <atom:updated>2018-07-31T05:12:46.597Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>This week in SimPEG…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2NNFiUjuCmP92uXLScPThQ.png" /></figure><p><strong>Dom </strong>has been working on making changes to the SimPEG Regularization for the new formulation of the TreeMesh including add functionality for mesh creation and refinement. The updates are included in pull request <a href="https://github.com/simpeg/simpeg/pull/708">#708</a>. This will be the topic of the upcoming SimPEG meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*07iezeepRfUUas3ZxgF3uw.png" /></figure><p><a href="https://medium.com/u/e8861949d0cf">SEOGI KANG</a>, <a href="https://medium.com/u/b6a74cd645c6">Doug Oldenburg</a> and myself (<a href="https://medium.com/u/3807e220bc10">Lindsey Heagy</a>) gave a course on Electromagnetic methods for exploration. The <a href="https://courses.geosci.xyz/houston2018">course slides</a> and <a href="https://www.youtube.com/playlist?list=PLd9tNwsUm9jMVKdVt_VDLkxS8qnTp4ONg">recordings of the lectures</a> are available. Much of the course material uses <a href="https://em.geosci.xyz/apps.html">Jupyter notebook apps that are built on SimPEG</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11bd0de6464c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simpeg/july-23-29-11bd0de6464c">July 23–29</a> was originally published in <a href="https://medium.com/simpeg">simpeg</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[July 9–15]]></title>
            <link>https://medium.com/simpeg/july-9-15-dcee6c865244?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcee6c865244</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[geoscience]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[geophysics]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Tue, 17 Jul 2018 05:07:15 GMT</pubDate>
            <atom:updated>2018-07-17T05:07:15.232Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>This week in SimPEG…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSMKOtZ6Q1XZK3-9IO5B4Q.png" /></figure><p><a href="https://medium.com/u/3807e220bc10"><strong>Lindsey Heagy</strong></a><strong>: </strong>I have been working on writing up some of the early PhD work I did on estimating the conductivity of a fractured volume of rock for a fracture operation with an electrically conductive proppant (particles used to keep the fractures open) and fluid. We approach it in 2 steps: (1) estimate the effective conductivity of a mixture of proppant and fluid, (2) estimate the (isotropic or anisotropic) conductivity of a fractured volume of rock filled with the conductive mixture. For both steps, we use self-consistent effective medium theory (which is now implemented as a Map in SimPEG… see: <a href="https://github.com/simpeg/simpeg/pull/706">https://github.com/simpeg/simpeg/pull/706</a>).</p><p>From there, we run a simple cross-well experiment on the cylindrically symmetric mesh (ignoring any steel casing) to see if the signal due to the fracture is detectable. The data plots show the secondary magnetic field for a range of source-receiver combinations for a survey conducted at 100Hz. Values below the noise floor of 10^-4 nT are not displayed. The semi-transparent overlay indicates the value of the secondary field as a percentage of the primary field: dark gray is 0–2%, white is 8–10%, and anything above 10% displays as fully transparent (e.g. if it is colored and fully transparent, we are confident we can detect the signal due to the fracture).</p><p>The notebooks used to generate these figures are available at: <a href="https://github.com/simpeg-research/heagy-2018-fracture-physprops">https://github.com/simpeg-research/heagy-2018-fracture-physprops</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hB3eBm5_R3JctWrfIK4w3w.png" /></figure><p><a href="https://medium.com/u/e8861949d0cf"><strong>SEOGI KANG</strong></a> has been working on a Linear inversion app to illustrate the fundamentals of (geophysical) linear inverse problems (e.g. non-uniqueness, misfit, priori information). The forward kernels consist of decaying oscillatory function, which imitates EM kernel (or EM green’s function). Further, this app allows users to explore some of the important parameters involved in a SimPEG inversion.</p><h3>New releases</h3><p>discretize 0.2.1 has been released as has SimPEG 0.9.0. This includes a 3D cylindrical mesh. Check out the release notes here:</p><ul><li><a href="https://github.com/simpeg/discretize/releases/tag/0.2.1">discretize 0.2.1</a></li><li><a href="https://github.com/simpeg/simpeg/releases/tag/0.9.0">SimPEG 0.9.0</a></li></ul><p>To upgrade:</p><pre>pip install --upgrade SimPEG</pre><h3><strong>At the meeting last week…</strong></h3><p>We discussed the <a href="https://github.com/simpeg/community">community repository</a> including a code of conduct, steps for creating a new repository, and contributor guidelines (see <a href="https://github.com/simpeg/community/pull/3">#3</a>)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fjn8Ub8mOS0E%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Djn8Ub8mOS0E&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fjn8Ub8mOS0E%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a037de4d507a73170c11e08f73d37c31/href">https://medium.com/media/a037de4d507a73170c11e08f73d37c31/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcee6c865244" width="1" height="1" alt=""><hr><p><a href="https://medium.com/simpeg/july-9-15-dcee6c865244">July 9–15</a> was originally published in <a href="https://medium.com/simpeg">simpeg</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Buenos Aires]]></title>
            <link>https://medium.com/disc2017/buenos-aires-a93714b4a4bd?source=rss-3807e220bc10------2</link>
            <guid isPermaLink="false">https://medium.com/p/a93714b4a4bd</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[earth-science]]></category>
            <category><![CDATA[geophysics]]></category>
            <category><![CDATA[open-science]]></category>
            <category><![CDATA[geoscience]]></category>
            <dc:creator><![CDATA[Lindsey Heagy]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 03:42:38 GMT</pubDate>
            <atom:updated>2018-06-27T03:42:38.367Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j-AhlkUvFL2uFWq0mAFVXA.png" /></figure><p><em>Nov 13–14</em></p><p>The morning after DISC Lab in <a href="https://medium.com/disc2017/mexico-city-d9a2fdd43c9">Mexico City</a>, we hopped on a flight to the Southern Hemisphere. Nine hours later, we landed in Buenos Aires. Buenos Aires is a city that is alive with music, tango, and festivals. Being spring, the Jacarandas were in bloom, giving a pop of purple to the city streets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CFQH71z2umidnxUpAnNVew.jpeg" /><figcaption>coffee with Ana at Cafe Tortoni</figcaption></figure><p>We arrived in Argentina on Wednesday evening and had a few days to be tourists in Buenos Aires and prep for the DISC. On Thursday afternoon, we met up with Ana Curcio, our local host, at Cafe Tortoni and chatted about applications of EM that would be of interest to participants in Argentina (as well as highlights we shouldn’t miss during our time in Buenos Aires!… more to come later in the blog).</p><h3>Day 1: DISC Course</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XM5dLYyN_QK7UyJVPf98iQ.png" /></figure><p>The majority of participants were industry professionals in the hydrocarbon industry and for most geoscientists in the room, seismic methods were the main method of focus in their day-to-day work. Several graduate students and professors from the University of Buenos Aires, some with backgrounds in EM, also attended.</p><p>Thanks to Ana’s efforts communicating details of the course to all of the participants, everyone who attended Day 1 also planned to attend Day 2. This enabled us to take the course at a more moderate pace, particularly as most participants had little background in electromagnetic methods. This also allowed us to cover all of the methods, in many locations, we have had to skip the presentations on either Ground Penetrating Radar or Natural Source methods due to time-constraints.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-z_ROTe87jdodDi5iofiCQ.png" /></figure><p>We started Day 1 at 9am with introductions from participants and then presented the <a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/0_Introduction.pdf">goals of the course and an introduction to electromagnetics and its applications</a>. From there, we successively covered <a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/1_dc_slides.pdf">direct current resistivity</a>, the <a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/2_EM_fundamentals.pdf">fundamentals of electromagnetics</a>, <a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/3_EM_inductive_sources.pdf">inductive sources</a> (including case histories in groundwater and hydrocarbon applications) and finished off the day with <a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/4_EM_grounded_sources.pdf">grounded sources</a> (including marine EM).</p><p>Empanadas were provided for the lunch break in the Pluspetrol offices — we always appreciate the when lunch is provided as it also gives us a chance to mingle and chat with more of the participants!</p><h3>Day 2: DISC Lab</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AyFmHdctll7sqXvur3wBKQ.png" /></figure><p>We picked up on day 2 with <a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/5_EM_natural_sources.pdf">natural source methods</a>. Magnetotellurics was of particular interest to many of the participants as several are involved in hydrocarbon exploration in Bolivia, where the target formation (the Huamampampa formation) is several kilometers beneath the surface. The significant tectonism and structure in the area makes the seismic very challenging to interpret. At this point, the potential of MT to play a role is still under investigation. A representative physical property model, followed by 3D numerical modelling is required to examine what information MT might bring to bear.</p><p>Following the wrap-up of the DISC course material, we turned the floor over to participants to discuss applications of EM they are working on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EWWzvoMwZK8fHJri_Efncg.png" /><figcaption>Ana Curcio</figcaption></figure><p><strong>Ana Curcio </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/disc_lab/Ana_SAG.pdf">slides</a>), with Proingeo, started us off with a presentation connected to groundwater. The Guarani Aquifer is located beneath the surface of Argentina, Uruguay, Paraguay, and Brazil. It is the second largest known aquifer system in the world covering an area about half a million square kilometers; its thickness of 50–800m and the maximum depth is about 1800m. Characterizing this aquifer, particularly its thickness and depth, is important. Ana showed examples of using MT to get estimates of these parameters. The interpretation was aided by the existence of drill holes accompanied with geologic logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fY97CyhxpGQ3slbB9qAyyQ.png" /><figcaption>Emilia Muzzio</figcaption></figure><p><strong>Emilia Muzzio</strong> (<a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/disc_lab/Muzzio_MetodoMT_Nov2008.pdf">slides</a>) — The venue for the DISC presentations was in a well-equipped room in Pluspetrol and we were pleased to hear a talk from Emilia, a geophysicist with Pluspetrol, about local hydrocarbon problems. The hydrocarbon areas for Argentina and Bolivia are characterized by large compressive anticlinal structures, but getting good geologic images from seismic surveys is problematic because of the complicated velocity model. MT surveys were carried out and the data inverted. The drilling of an exploratory well was in progress but, with the interpretation of the MT, it was decided to deviate the well to more directly intersect the sides of the anticline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZNZbpzCAtuTu9csvDG8--g.png" /><figcaption>Liliana Curso</figcaption></figure><p><strong>Liliana Curso </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/disc_lab/liliana_curso_EM.pdf">slides</a>) — The area of Taco Ralo, at the eastern border of the Andes in Argentina, is an important geothermal resource that results from deep tectonic and magmatic activity. There is no surface volcanism but high temperature waters exist at depth. Liliana, a graduate student at University of Buenos Aires and her coworkers have acquired MT data over the region. Liliana’s research is focussed on inverting and interpreting those data. The work is in progress and is currently exploring the effects of topography on the MT inversions using the ModEM software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUA_vaNfnkwmlY-fYr6c4A.png" /><figcaption>Franco Macchioli Grande</figcaption></figure><p><strong>Franco Macchioli Grande </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/disc_lab/franco_jornada-hpc.pdf">slides</a>), who is a PhD student at Facultad de Ciencias Astronómicas y Geofísicas, UNLP, is developing numerical algorithms for forward modelling and inversion of controlled EM sources, with particular application to marine problems. He’s using a primary/secondary field formulation and solving with finite elements. A stochastic framework is used for the inversion. His work is currently in 2D but he plans to extend the research to generate a 3D inversion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MwwMCoj1aJMQKOx2Brtfag.png" /></figure><p><strong>Juanpablo Romero </strong>(<a href="https://storage.googleapis.com/simpeg/disc2017/buenos-aires/disc_lab/Case_GPR_Santa_Ana.pdf">slides</a>) finished off the presentations for the day. South America has many historic buildings and archaeological sites where structures are to be determined and, sometimes, restored. An ancient church, built in 1752, and declared a heritage site in 1959, was one of the buildings that needed restoration. The church, located in the town of Santa Ana in Venezuela, had undergone many modifications over the centuries and the engineering challenge was to restore it. That presented many challenges because details about previous versions of the church were not available. From the engineers perspective, they wanted a least invasive technique to inform them about the potential of buried bodies, objects, and general structure. GPR was an obvious choice and Juanpablo, with the Universidad Central De Venezuela, was in charge of survey design and carrying out the acquisition and analysis. An interesting offshoot of this case history was how the interaction between a geophysicist, who understands the technique and strengths and limitations, and an engineer, who does not know the technology, communicate and build a mutual trust.</p><p>We wrapped up day 2 with an overview of resources available to participants, including <a href="https://em.geosci.xyz/">EM GeoSci</a>, a “textbook” resource on the fundamentals of electromagnetics and <a href="http://simpeg.xyz/">SimPEG</a>, open source software for simulations and inversions, as well as ways to keep in touch through the <a href="http://slack.geosci.xyz/">GeoSci slack channel</a> and the <a href="https://groups.google.com/forum/#!forum/simpeg">SimPEG Google group</a>.</p><h4>From the Participants</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yeuyvQiOmrcMFhLD-3L1jw.png" /><figcaption>lunch on day 2 of the DISC</figcaption></figure><p><em>“It has been very interesting to get to know the advances in EM methods and the perspective of [their] usage in the future. The use of web simulation tools makes a great difference in understanding the fundamentals of each case.” </em>— Juanpablo Romero, Geophysicist</p><p><em>“It was very useful, especially for recognizing the advantages and limitations of each technique discussed. It’s great to see real examples and applications”</em> — Juan Ignacio Gómez, Geophysicist</p><p><em>“[The course] has a lot of value. You brought enthusiasm for communicating the power of EM methods. I hope all of the audiences have appreciated it! The course is well structured and encouraged us all to think. Perhaps it is a bit long for one or two days, but EM is a huge topic for two days only!” </em>— Franco Macchioli Grande, PhD student</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OS3XMWV4_7Gf3sXe2-rHXw.png" /><figcaption>Participants of DISC Buenos Aires</figcaption></figure><p>All of the material from the course is available at: <a href="https://disc2017.geosci.xyz/buenos-aires">https://disc2017.geosci.xyz/buenos-aires</a>.</p><h3>A few adventures</h3><p>We landed in Buenos Aires on Wednesday night and the DISC was scheduled for the following Monday and Tuesday, so the weekend gave us a couple extra free days to do a bit of catch-up on emails, but mostly to explore the city and find out what it has to offer!</p><h4>Thursday</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WYlZUuTV3WMfMjby1tRxAQ.png" /></figure><p>On Thursday, our first full day in Buenos Aires, we went out for a walk to explore the neighbourhood around our accommodation and stopped along the way for some empanadas at a local Parrilla. We also stopped by a produce shop to pick up some fresh fruits and vegetables (to balance out all of the beef!). That afternoon, we met up with Ana at Cafe Tortoni, an iconic cafe that also hosts Tango shows in the evenings. We chatted about applications of geophysics in Argentina as well as what some of the highlights to see during our time in Buenos Aires.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b7tVua-jMVtcYknep69cYA.png" /></figure><p>That evening, Ana had made reservations for all of us to attend a show at Tango Porteno. The evening started off with a lesson on the tango basic steps; this was followed by steak dinner (when in Argentina!) and the spectacular show.</p><h4>Friday</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7LMuZFe7hG6B95D7_jGNag.png" /><figcaption>Walking through San Telmo (far left), modern art museum (left of centre), spiderweb display at the modern art museum (right of centre), Parque Lezama (far right)</figcaption></figure><p>On Friday, we did a self-guided walking tour. We started off in San Telmo, the area we were staying in. San Telmo is the oldest neighbourhood in Buenos Aires; its cobblestone streets are lined with antique shops and parrillas (traditional Argentinian barbecues). It is also home to the Modern Art museum. On the top floor of the museum, there was a dark room which you could walk around the perimeter of. The rest of the room was filled with by the exhibition: the wold’s largest indoor spider web. It was built by eighteen colonies of spiders over 4 months — quite spectacular!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ky71N5eVsXIeYzlcysA0Iw.png" /><figcaption>La Boca</figcaption></figure><p>From there, we made our way through Parque Lezama towards the La Boca neighbourhood of Buenos Aires. La Boca is home to the famous street: El Caminito that is lined with brightly coloured buildings; the area buzzes with music and art (and a few tourist traps, as with any iconic spot)!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F1FZfmp_K8purmPaFgEt9Q.png" /><figcaption>so much steak.</figcaption></figure><p>We finished off the day in Argentinian style. That evening, we went to a Des Nivel, a parrilla recommended to us by our airbnb host. We ordered a couple steaks and headed out with plenty of left-overs.</p><h4>Saturday</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*27QUWCjrCDWQa4_v7ii5Qg.png" /><figcaption>Recoleta (far left), Choripan for lunch (centre), Jacarandas trees in bloom (far left)</figcaption></figure><p>Going to a cemetery hardly seems like a tourist attraction, but visiting the Recoleta cemetery was recommended to us by a number of people. So Saturday, we headed to Recoleta. There are thousands of mausoleums there, including some famous figures such as Eva Perón, some command your attention while others seemed much more personal. It is a truly unique site.</p><p>Following our visit to Recoleta, we wandered through the street market outside the cemetery, stopping for a Choripan (chorizo sandwich with grilled veggies — quite tasty!). We started walking towards the museum of Latin American Art, which hosts art from Frida Kahlo and Diego Rivera. After seeing the long line-up to get in, we decided to instead continue walking the streets, photograph some of the Jacarandas in their beautiful, purple bloom, and stop to listen to music at some of the Saturday street festivals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QoHU-jf5SnKU_877K1E6tw.png" /><figcaption>Street food festival</figcaption></figure><p>On Ana’s recommendation, we spent the rest of the afternoon and in to the evening at a street food festival (thanks Ana!!). Inside, there was a market where you could buy (and sample!) local produce, cheese, meats, tea’s, … Outside, there were dozens and dozens of food stands and food trucks. We sampled Buñuelos (corn fritters), Proveleta (an Argentinian staple at many parrillas. It is fried provolone cheese — can’t go wrong with that!), and a beef Arepa. We certainly didn’t go home hungry.</p><h4>Sunday</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGQ5BOvTAXLF6Wi_73OYTA.png" /><figcaption>Market near Plaza de Mayo (left), view of Plaza de Mayo from the museum (right of centre), English tower (far right)</figcaption></figure><p>Sunday was our last day before the DISC. After a bit of prep for the course, we headed out to meet up with Ana. We met at a Sunday market near Plaza de Mayo, the town square famous for marking Argentinian independence. The sight-lines draw your attention to the Pirámide de Mayo, which was erected on the one-year anniversary of Argentinian Independence, and just beyond that, the Presidential Palace. At the other end of the plaza is history museum, which we spent some time walking through. From there, we made our way to see the English clock tower.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ww9pjxXnpQV31uv42EtOZw.png" /><figcaption>Market at Plaza Dorrego</figcaption></figure><p>Our last stop of the day was the Sunday market at Plaza Dorrego. Doug came home with a new apron, and I came back with a new scarf! As the market was wrapping up, we sat down for a pizza dinner and once the stalls were down, we enjoyed listening to music, and watching as people filled the square to dance tango in the street. It was a wonderful way to end our tourist time in Argentina.</p><h3>Thanks</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9hHdPKU5aBIDlo8tL82ibg.png" /><figcaption>Ana Curcio and Doug Oldenburg</figcaption></figure><p>Ana was an exceptionally enthusiastic local host! We are very grateful to her for getting the word out to participants and for the time she took to show us a wonderful time in Buenos Aires.</p><p>Thanks also to <a href="http://www.pluspetrol.net/">Pluspetrol</a> for providing the facility and technical support for running the course in Buenos Aires.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a93714b4a4bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/disc2017/buenos-aires-a93714b4a4bd">Buenos Aires</a> was originally published in <a href="https://medium.com/disc2017">DISC 2017</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>