User Tools

Site Tools


ideas_page

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ideas_page [2016/02/23 18:21]
unoebauer [New module for the creation of spectra]
ideas_page [2016/04/04 18:29] (current)
wkerzend
Line 23: Line 23:
 ===== List of GSoC 2016 project ideas ===== ===== List of GSoC 2016 project ideas =====
  
-In the TARDIS collaboration we first establish a detailed plan on implementing new features before starting the actual work. This is an important step that ensures that the entire TARDIS collaboration is informed about the development efforts and that the team members can help shape the ideas during the discussion phase. We call these documents ​TNo PEP - TARDIS Enhancement Proposals. We already have a great list of ideas at https://​github.com/​tardis-sn/​tep that we need help with. Some of these we have specially selected for GSoC 2016 and are listed with specific "​warm-up"​ tasks below. But feel free to propose your own TEP and make a PR on that. +In the TARDIS collaboration we first establish a detailed plan on implementing new features before starting the actual work. This is an important step that ensures that the entire TARDIS collaboration is informed about the development efforts and that the team members can help shape the ideas during the discussion phase. We call these documents ​TEP - TARDIS Enhancement Proposals. We already have a great list of ideas at https://​github.com/​tardis-sn/​tep that we need help with. Some of these we have specially selected for GSoC 2016 and are listed with specific "​warm-up"​ tasks below. But feel free to propose your own TEP and make a PR on that. 
  
-If you use one of our TEPs, you can definitely add more detail to the implementation,​ but what we really want to see is a detailed timeline with milestones that shows us that you have thought about how to implement the feature in three months. For any questions about the projects, please ask on our mailing list [[https://​groups.google.com/​forum/#​!forum/​tardis-gsoc-2016|tardis-gsoc-2016@googlegroups.com]] or on [[https://​gitter.im/​tardis-sn/​tardis|Gitter]].+If you use one of our TEPs, you can definitely add more detail to the implementation,​ but what we really want to see is a detailed timeline with milestones that shows us that you have thought about how to implement the feature in three months. For any questions about the projects, please ask on our mailing list [[https://​groups.google.com/​forum/#​!forum/​tardis-gsoc-2016|tardis-gsoc-2016@googlegroups.com]] or on [[https://​gitter.im/​tardis-sn/​tardis|Gitter]].  
 + 
 +Putting in a Pull Request with the First objective is essential for each proposal to allow to see how you work
  
 ---- ----
Line 76: Line 78:
 ==== Atomic Datasets ==== ==== Atomic Datasets ====
  
-**Difficulty:​** ​Moderate+**Difficulty:​** ​Hard
  
-**Astronomy knowledge needed:​** ​None/Low - might be helpful+**Astronomy knowledge needed:​** ​Medium
  
 **Mentors:​** @lukeshingles,​ @shaching **Mentors:​** @lukeshingles,​ @shaching
Line 122: Line 124:
 This project requires a bit of physics knowledge. This project requires a bit of physics knowledge.
  
-**Your first objective if you choose to accept the mission:** Implement a simple counting estimator, storing the number of Monte Carlo packets that come into resonance with each atomic line transition. For this, look into the main Monte Carlo part of TARDIS and find the location where the ''​j_blue_estimators''​ are incremented. This would be a good place to insert your counters. "Bonus objective:"​ Once the counter is properly working, you could try to implement an estimator for the line absorption rates (see Equation 11 in [[http://​adsabs.harvard.edu/​cgi-bin/​nph-data_query?​bibcode=1999A%26A...345..211L&​link_type=ARTICLE&​db_key=AST&​high=|Lucy 1999]]). In an additional step, these level absorption rates could be used to calculate level absorption rates (see Equation 19 in [[http://​adsabs.harvard.edu/​cgi-bin/​nph-data_query?​bibcode=1999A%26A...345..211L&​link_type=ARTICLE&​db_key=AST&​high=|Lucy 1999]]).+**Your first objective if you choose to accept the mission:** Implement a simple counting estimator, storing the number of Monte Carlo packets that come into resonance with each atomic line transition. For this, look into the main Monte Carlo part of TARDIS and find the location where the ''​j_blue_estimators''​ are incremented. This would be a good place to insert your counters. ​ 
 + 
 +"Bonus objective:"​ Once the counter is properly working, you could try to implement an estimator for the line absorption rates (see Equation 11 in [[http://​adsabs.harvard.edu/​cgi-bin/​nph-data_query?​bibcode=1999A%26A...345..211L&​link_type=ARTICLE&​db_key=AST&​high=|Lucy 1999]]). In an additional step, these level absorption rates could be used to calculate level absorption rates (see Equation 19 in [[http://​adsabs.harvard.edu/​cgi-bin/​nph-data_query?​bibcode=1999A%26A...345..211L&​link_type=ARTICLE&​db_key=AST&​high=|Lucy 1999]]). 
 + 
 +**Hints:** As mentioned above, understanding what incrementing ''​j_blue_estimators''​ means, is the key to the first objective. Physically, it measures the energy of all photons which can come into resonance with a particular line. Photons/​packets not necessarily have to interact with the line to be counted. The relativistic Doppler shift just has to shift their frequency far enough so that it matches the frequency of the line. Taking all this into account, you will realise that the ''​j_blue_estimators''​ behave very similar to the counter you are supposed to implement. ​  
  
 ---- ----
ideas_page.1456248119.txt.gz · Last modified: 2016/02/23 18:21 by unoebauer