https://www.reproducibility.org/wiki2020/api.php?action=feedcontributions&user=Bert&feedformat=atomMadagascar - User contributions [en]2024-03-29T06:12:31ZUser contributionsMediaWiki 1.34.0https://www.reproducibility.org/wiki2020/index.php?title=Delft_2009&diff=663Delft 20092009-03-02T11:38:12Z<p>Bert: Added OpendTect's contribution</p>
<hr />
<div><center><big>'''Madagascar School on Reproducible Computational Geophysics'''</big><br />
<br />
[[Image:View-of-delft.jpg]]<br />
<br />
<hr><br />
<br />
<br />
{| align="center" border="1" cellpadding="5" cellspacing="0" <br />
! colspan="3" style="background:#ffdead;" | Program<br />
|-<br />
! Day 1 <br />
! colspan="2" style="background:#efefef;" | Friday, June 12<br />
|-<br />
| 9:00-12:00<br />
! colspan="2" | Madagascar as a framework for reproducible research<br />
|-<br />
|<br />
| colspan="2" | <br />
<tt>Madagascar</tt> provides a complete environment for organizing one's research, from new software development to running computational experiments to publishing the experimental results in papers and reports and archiving them for future usage. This shared environment enables an efficient exchange of research results with colleagues and sponsors. In this module, you will learn how to take the full advantage of the <tt>Madagascar</tt> environment to enhance research productivity and research collaboration.<br />
|-<br />
| 13:00-16:00<br />
! colspan="2" | Seismic interpretation (via [http://opendtect.org OpendTect] and <tt>Madagascar</tt>)<br />
|-<br />
|<br />
| colspan="2" |<br />
The usage domain for Madagascar traditionally is seismic processing. Products will go off to some form of interpretation. This module will provide an overview of the interpretation process, what interpreters need and what they produce. OpendTect is an Open Source tool that covers the basic interpretation work flow. With its open architecture, everyone can make extensions of the functionality with plugins (in C++ or even C). Recently, the Madagascar connection plugin was added to OpendTect which gives access to the Madagascar programs in an easy GUI-driven way. This broadens the scope of Madagascar, enabling all kinds of processing still necessary to further investigate the data or to refine the processing. The Madagascar plugin is discussed, plugin building in general, and implications for future developments in Madagascar.<br />
|-<br />
! Day 2 <br />
! colspan="2" style="background:#efefef;" | Saturday, June 13<br />
|-<br />
| 9:00-12:00<br />
! colspan="2" | Wavefield seismic imaging <br />
|-<br />
|<br />
| colspan="2" | <br />
The theoretical part of this module provides an overview of reverse-time imaging methodology applied to wavefield seismic data. The main technique discussed is reverse-time migration with emphasis on modern imaging conditions which enable migration velocity analysis and amplitude-versus-angle analysis. The applied part demonstrates this technique on a complex geologic model using <tt>Madagascar</tt> codes in a fully reproducible setup.<br />
|-<br />
| 13:00-16:00<br />
! colspan="3" | Seismic interferometry<br />
|-<br />
|<br />
| colspan="3" | <br />
In this module, we will discuss theoretical aspects of seismic interferometry in the context of scattering problems with applications for imaging and monitoring. Using <tt>Madagascar</tt>, we will build fully reproducible numerical experiments, using different models and acquisition geometries, that provide examples and insights into interferometry of scattered fields.<br />
|-<br />
|}<br />
<br />
</center><br />
<br />
== Location ==<br />
<br />
[[Image:TU.gif|left]]<br />
<br />
Department of Geotechnology<br><br />
Delft University of Technology (TU Delft)<br><br />
The Netherlands<br clear="all"><br />
<br />
== Instructors ==<br />
<br />
* Sergey Fomel (University of Texas at Austin)<br />
* Paul Sava (Colorado School of Mines)<br />
* Ivan Vasconcelos (ION Geophysical)<br />
* Arnaud and Hélène Huck (dGB Earth Sciences)<br />
<br />
== Registration ==<br />
<br />
Attendance is free but registration is required. To register, please send [mailto:rsfschool@gmail.com an email].</div>Berthttps://www.reproducibility.org/wiki2020/index.php?title=Delft_2009&diff=635Delft 20092009-02-09T22:54:41Z<p>Bert: Just changed the title of the OpendTect-related part</p>
<hr />
<div><center><big>'''Madagascar School on Reproducible Computational Geophysics'''</big><br />
<br />
<hr><br />
<br />
{| align="center" <br />
! colspan="3" style="background:#ffdead;" | Program<br />
|-<br />
! Day 1 <br />
! colspan="2" | Friday, June 12<br />
|-<br />
|<br />
! colspan="3" | Madagascar as a framework for reproducible research<br />
|-<br />
|<br />
! colspan="3" | Madagascar and Seismic interpretation (via OpendTect)<br />
|-<br />
! Day 2 <br />
! colspan="2" | Saturday, June 13<br />
|-<br />
|<br />
! colspan="3" | Seismic imaging<br />
|-<br />
|<br />
! colspan="3" | Seismic interferometry<br />
|-<br />
|}<br />
<br />
</center><br />
<br />
== Location ==<br />
<br />
[[Image:TU.gif|left]]<br />
<br />
Department of Geotechnology<br><br />
Delft University of Technology (TU Delft)<br><br />
The Netherlands<br clear="all"><br />
<br />
== Instructors ==<br />
<br />
* Sergey Fomel (University of Texas at Austin)<br />
* Paul Sava (Colorado School of Mines)<br />
* Ivan Vasconcelos (ION Geophysical)<br />
<br />
== Registration ==<br />
<br />
Details to follow.</div>Berthttps://www.reproducibility.org/wiki2020/index.php?title=Seismic_Library&diff=634Seismic Library2009-02-09T22:43:51Z<p>Bert: </p>
<hr />
<div>== SeismIO ==<br />
<br />
<br />
==== Imagine ====<br />
Imagine a world where seismic data access is a done deal. Because of a de-facto, free, easy-to-use library made by a group of enthusiasts. A truly open, usable and free Open Source initiative. No pile of format descriptions, no fat libraries intended for other purposes, just seismic data - read and write. Something that works from day one.<br />
<br />
==== Aims ====<br />
''You can't always get what you want. But sometimes, you get what you need.''<br />
* The fastest-trace-in-town? No chance anyway. But pretty fast ''is'' cool.<br />
* Super-slim super-compressed files? Nah. But deep down we know that size ''does'' matter.<br />
* The richest feature set? Hmmm. Self-describing, extensible is nice.<br />
<br />
==== Real aims ====<br />
OK, but what aims are 'rock-hard'?<br />
# As many people as possible benefit. From acquisition to interpretation, from university to contractor, from researcher to IT professional, from beginning student to the highly experienced software developer.<br />
# Data once written will be readable. Always. And you know what you're getting. Always.<br />
# The library is easy to use. As easy as possible. Not easier than that.<br />
<br />
==== Rules ====<br />
There are no hidden agenda's. If you're in, you will strive to help the aims set above. Employers, money, old habits? In doubt, you go against those. Just to keep a clean conscience.<br />
<br />
==== How? ====<br />
You can sit behind your screen and specify formats and interfaces days, weeks, months - until you're blue in the face. Documents grow, and every model you make is more beautiful than the previous. Then finally, your models are good enough so you can start programming. Oops. Within a few days you've proven that your models are wrong. You've learned the hard way what thousands of professionals ignore day-in-day-out: it doesn't work that way.<br />
<br />
==== So, how? ====<br />
<br />
Specifications in our sort of environments develop during actual software development. What you can do, is make one<br />
or a couple of documents scanning the problem domain, identifying what kinds of problems are the likely ones that need to be grappled with. Things like: what sort of data and procedures are common in acquisition,<br />
processing and interpretation? How does this differ from research to hard-core production work? Or this one: what computer language(s) is/are the target(s)?<br />
<br />
Therefore, we'd need input from many sides, from people who are willing to put aside their economic, emotional and historical stakes - but rather approach the problem from the more philosophical side. The result is an inventory of<br />
knowledge, tensions, existing techniques, resources, visions, ... and take it from there.<br />
<br />
Then, start cracking. The Open Source way is to specify by implementing. A function that works is worth a thousand words of specification. Read about the [http://www.martinfowler.com/articles/newMethodology.html Agile] way, and pick up the good bits. Keep communicating, and improving. Prepare for change; in particular, make sure the data versioning system is brilliant. Contribution is great but keep the evil forces away.<br />
<br />
==== Why? ====<br />
<br />
Why do this? Why invest time and effort? There are free libs around. Pick one and get over it.<br />
<br />
* What are these zillion other routines? When will the build finish?<br />
* Everybody can see that my lib is the best. Other people must be idiots!<br />
* Oh, I thought it was free and open and LGPL?<br />
* Duh! This stuff is <u>hard</u>!<br />
* This code must have been made when seismograms were still analog!<br />
* Huh? They now adopted some kind of brain-dead 'standard'?<br />
<br />
Let's face it. Seismic data needs a base library with no strings attached. It needs to be free and usable. It needs to be neutral. It needs to get the job done. We need to make it.</div>Berthttps://www.reproducibility.org/wiki2020/index.php?title=Seismic_Library&diff=633Seismic Library2009-02-09T22:19:28Z<p>Bert: </p>
<hr />
<div>== SeismIO ==<br />
<br />
<br />
==== Imagine ====<br />
Imagine a world where seismic data access is a done deal. Because of a de-facto, free, easy-to-use library made by a group of enthusiasts. A truly open, usable and free Open Source initiative. No pile of format descriptions, no fat libraries intended for other purposes, just seismic data - read and write. Something that works from day one.<br />
<br />
==== Aims ====<br />
''You can't always get what you want. But sometimes, you get what you need.''<br />
* The fastest-trace-in-town? No chance anyway. But pretty fast ''is'' cool.<br />
* Super-slim super-compressed files? Nah. But deep down we know that size ''does'' matter.<br />
* The richest feature set? Hmmm. Self-describing, extensible is nice.<br />
<br />
== Real aims ==<br />
OK, but what aims are 'rock-hard'?<br />
# As many people as possible benefit. From acquisition to interpretation, from university to contractor, from researcher to IT professional, from beginning student to the highly experienced software developer.<br />
# Data once written will be readable. Always. And you know what you're getting. Always.<br />
# The library is easy to use. As easy as possible. Not easier than that.<br />
<br />
== Rules ==<br />
There are no hidden agenda's. If you're in, you will strive to help the aims set above. Employers, money, old habits? In doubt, you go against those. Just to keep a clean conscience.<br />
<br />
== How? ==<br />
You can sit behind your screen and specify formats and interfaces days, weeks, months - until you're blue in the face. Documents grow, and every model you make is more beautiful than the previous. Then finally, your models are good enough so you can start programming. Oops. Within a few days you've proven that your models are wrong. You've learned the hard way what thousands of professionals ignore day-in-day-out: it doesn't work that way.<br />
<br />
== So, how? ==<br />
<br />
Specifications in our sort of environments develop during actual software development. What you can do, is make one<br />
or a couple of documents scanning the problem domain, identifying what kinds of problems are the likely ones that need to be grappled with. Things like: what sort of data and procedures are common in acquisition,<br />
processing and interpretation? How does this differ from research to hard-core production work? Or this one: what computer language(s) is/are the target(s)?<br />
<br />
Therefore, we'd need input from many sides, from people who are willing to put aside their economic, emotional and historical stakes - but rather approach the problem from the more philosophical side. The result is an inventory of<br />
knowledge, tensions, existing techniques, resources, visions, ... and take it from there.<br />
<br />
Then, start cracking. The Open Source way is to specify by implementing. A function that works is worth a thousand words of specification. Read about the [http://www.martinfowler.com/articles/newMethodology.html Agile] way, and pick up the good bits. Keep communicating, and improving. Prepare for change; in particular, make sure the data versioning system is brilliant. Contribution is great but keep the evil forces away.</div>Berthttps://www.reproducibility.org/wiki2020/index.php?title=Seismic_Library&diff=632Seismic Library2009-02-09T21:38:06Z<p>Bert: </p>
<hr />
<div>== SeismIO ==<br />
<br />
<br />
==== Imagine ====<br />
Imagine a world where seismic data access is a done deal. Because of a de-facto, free, easy-to-use library made by a group of enthusiasts. A truly open, usable and free Open Source initiative. No pile of format descriptions, no fat libraries intended for other purposes, just seismic data - read and write.<br />
<br />
==== Aims ====<br />
''You can't always get what you want. But sometimes, you get what you need.''<br />
:The fastest trace-in-town? No chance. But pretty fast - cool.<br />
:Super-slim super-compressed files? Nah. But deep down we know that size does matter.<br />
:The richest feature set? Hmmm.<br />
<br />
== Real aims ==<br />
OK, but what aims are 'rock-hard'?<br />
# As many people as possible benefit. From acquisition to interpretation, from university to contractor, from researcher to IT professional, from beginning student to highly the highly experienced software developer.<br />
# Data once written will be readable. Always. And you know what you're getting. Always.<br />
<br />
== Rules ==<br />
There are no hidden agenda's. If you're in, you will strive to help the aims set above. Employers, money, old habits? In doubt, you go against those. Just to keep a clean conscience.<br />
<br />
==</div>Bert