ideas_page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ideas_page [2019/02/06 04:25] wkerzend |
ideas_page [2019/03/12 00:04] (current) wkerzend |
||
|---|---|---|---|
| Line 51: | Line 51: | ||
| We have two types of tests: unit tests that verify small portions of the code and full-scale integration tests. Both of these test types are implemented with a framework. But the integration tests are difficult to use. | We have two types of tests: unit tests that verify small portions of the code and full-scale integration tests. Both of these test types are implemented with a framework. But the integration tests are difficult to use. | ||
| - | * currently we mainly run the integration tests on an external server. We want to integrate them into our general TRAVIS continuous integration routine. We'd also like to expand that and check also different properties of our model against reference data (e.g. electron densities, ionization fractions, dilution factors) | + | * currently we mainly run the integration tests on an external server. We want to integrate them into our general Azure Pipeline continuous integration routine. We'd also like to expand that and check also different properties of our model against reference data (e.g. electron densities, ionization fractions, dilution factors) |
| * hand in hand with expanding the verification process we will improve the reporting process which should contain detailed plots and comparison results. A framework exists but is currently not actively used. | * hand in hand with expanding the verification process we will improve the reporting process which should contain detailed plots and comparison results. A framework exists but is currently not actively used. | ||
| - | **Your first objective if you choose to accept the mission:** Setup the integration tests to run once a week on travis given the examples at https://tardis.readthedocs.io/en/latest/running_tests.html | + | **Your first objective if you choose to accept the mission:** Setup the integration tests to run once a week on Azure pipelines given the examples at https://tardis.readthedocs.io/en/latest/running_tests.html |
| ---- | ---- | ||
| Line 94: | Line 94: | ||
| **Astronomy knowledge needed:** Low/None | **Astronomy knowledge needed:** Low/None | ||
| - | **Mentors:** Stuart Sim, Yssa Camacho | + | **Mentors:** Yssa Camacho, Stuart Sim |
| **Programming skills**: Python | **Programming skills**: Python | ||
| Line 166: | Line 166: | ||
| **Your first objective if you choose to accept the mission:** Use dask to run distributed TARDIS instances in parallel on your system. Use http://distributed.dask.org/en/latest/client.html as a guide to make a simple example. | **Your first objective if you choose to accept the mission:** Use dask to run distributed TARDIS instances in parallel on your system. Use http://distributed.dask.org/en/latest/client.html as a guide to make a simple example. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Improve the C/Python interface ==== | ||
| + | |||
| + | **Difficulty:** Hard | ||
| + | |||
| + | **Astronomy knowledge needed:** None | ||
| + | |||
| + | **Mentors:** Wolfgang Kerzendorf, Christian Vogl | ||
| + | |||
| + | **Programming skills:** python, cython | ||
| + | |||
| + | |||
| + | **GSoC Application Tag:**c_interface | ||
| + | |||
| + | **Description:** TARDIS is a hybrid code built on C/Cython/Python. Currently, there is a lot of interface code to port the python data structures from Python via Cython to C. This makes the code cumbersome to test and try out new things. There are now several new ways that promise to make this easier. We want to try to use cFFI and Apache Arrow to do this. | ||
| + | |||
| + | **Your first objective if you choose to accept the mission:** use cFFI to provide an automatic interface for testing the parts in the montecarlo package instead of ctypes. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Profile TARDIS ==== | ||
| + | |||
| + | **Difficulty:** Easy/Moderate | ||
| + | |||
| + | **Astronomy knowledge needed:** None | ||
| + | |||
| + | **Mentors:** Wolfgang Kerzendorf | ||
| + | |||
| + | **Programming skills:** python, cython | ||
| + | |||
| + | |||
| + | **GSoC Application Tag:**asv | ||
| + | |||
| + | **Description:** TARDIS is a code that prides itself on being relatively fast to compute a synthetic spectrum. We are also continuously adding additional microphysics in the code which sometimes requires additional calculation. It is important to understand how much this microphyiscs adds to the runtime of the code. For this we want to implement a benchmark in asv (airspeed velocity) that can automatically generate a report for us. | ||
| + | |||
| + | **Your first objective if you choose to accept the mission:** implement a simple benchmark in asv. | ||
| + | |||
| + | |||
ideas_page.1549423538.txt.gz ยท Last modified: 2019/02/06 04:25 by wkerzend
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
