2017 MHD Workshop

From Einstein Toolkit Documentation
Revision as of 11:07, 3 February 2017 by Eschnett (talk | contribs) (FunHPC parallelization progress)
Jump to: navigation, search

Workshop in New York City and at Columbia University.

Chelsea Venue

  • On the first afternoon, we'll meet off-campus to get the workshop started.
  • We will start at 14:00.
  • We have a conference room for 8 booked under Christian D. Ott, California Institute of Technology at
    Select Office Suites Chelsea
    116 W 23rd St, New York, NY 10011
    https://goo.gl/maps/WDBNQpwadfE2
    From Columbia, the best way to get there is to take Subway Line 1 to 23rd Street Station.

Columbia Venue

  • The workshop will take place in the Conference Room of the Center for Theoretical Physics at Columbia. The Conference Room (Room 907) is located on the 9th floor of the Physics building (Pupin Laboratories).
  • Street address: 538 West 120th Street, New York, NY 10027
  • Note that the main entrance is on the Campus Level (5th floor, south side) as indicated here:

map

  • You can enter Campus at 116th/Broadway. There is also the possibility of entering Pupin Hall from 120th/Broadway. In this case, enter through the North West Corner Building and take the stairs/escalators up to the Campus level, exit the building and enter Pupin through the main entrance.
  • The conference room has a board and a big presentation screen -> There is the possibility of giving a black board talk or a slide presentation, or a combination of both.

Time and Agenda

Monday
2:00 — 2:10: Welcome
2:10 — 2:35: Philipp to talk on flux CT
2:35 — 3:00: Daniel to talk on vector potential and MHD con2prim
3:00 — 3:25: (Propose switch with Christian's talk) David to talk on DG and Zelmani M1
3:25 — 3:55: Coffee break
3:55 — 4:20: (Propose switch with David's talk) Christian to talk on M1 work/results
4:20 — 4:45: Erik: FunHPC — current state, toward AMR, toward KNL
4:45 — 5:10: Roland: HydroFunToy — code design and capability
5:10 — 5:45: Closing discussion and roadmap for the week

Tuesday to Thursday
9:00 am till late: “workshop” -> work on topics identified on Monday

Friday
9:00 — 11:00: Wrap it up
11:00 — 12:30: Summary of the workshop and defining future directions/coordinate future work
12:30: lunch/end of workshop

  • You are free to arrive earlier on Monday and leave later on Friday, we have the room booked for the entire day.
  • Let me know if this tentative agenda conflicts with any of your travel plans, we can reschedule things.

Talks

  • The talks on Monday afternoon are meant to be informal kick-off talks in order to start the discussion in a well defined way and to identify the topics/aspects that we want to work on in the following days (or that we want to keep in mind while working on other aspects). I’d suggest that we keep them fairly short (no more than ~20-25 mins including some discussion), just trying to provide a basic introduction that brings everyone onto the same page, addressing the following basic questions like:
    • What is the analytic formulation (basic intro to the equations — if applicable)?
    • What is the current status, or what have people been working on so far?
    • What are the short & long-term goals? What do we need to implement/what needs to be done to move forward?
    • What do you think could be the specific goals for the week?
  • Please check and update the title of your talk you volunteered for (see above)
  • Feel free to add some notes/thoughts/ideas regarding your talk on the wiki

Knights Landing on Stampede

David Radice's simfactory replacement: https://bitbucket.org/dradice/batchtools

flux-CT implementation progress

  • Identified which equations to solve and that there is indeed a Riemann problem to solve for the electric field
  • This is not a Riemann problem for the state vector (which is the magnetic field), but the electric field is used to update the magnetic field
  • The Riemann problem for the electric field requires reconstruction of the velocity and magnetic field to the cell edge, requiring a double reconstruction for the velocity
  • Started implementation for that and bookkeeping is going to be tedious but otherwise implementation should be straightforward
  • Need to come up with good test cases to make sure this is implemented correctly

FunHPC parallelization progress

  • Continued to make FunHPC work, as alternative to OpenMP
  • Improve performance by taking cache alignment into account
  • * Many internal modifications to Cactus and Carpet
  • Benchmarking
  • * Need to measure performance details automatically, make available to users