Differences

This shows you the differences between two versions of the page.

--- ideas_page [2019/03/09 22:52]
wkerzend
+++ ideas_page [2019/03/12 00:04]
wkerzend
@@ 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.
+----
+==== 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.

TARDIS GSoC 2019

User Tools

Site Tools

Differences

Page Tools