Application for Attendance

All participants must apply to attend.  Attendance is limited.

Additional instructions:

  • Estimate your airfare to Ontario International Airport (ONT).
  • All Applicants must apply for support for Workshop Fees.
  • All Applicants must agree to the code of conduct.

Participants will be notified beginning April 1, 2018 of their application status.

Code of Conduct [link]

CIG supports a variety of activities, online and in person, to foster best practices in scientific software development and promote learning, networking, and collaboration. We value the participation of every member of the community and want all participants to have an enjoyable and fulfilling experience in their interactions with the CIG community.  Accordingly, all who participate in CIG activities are expected to show respect and courtesy to others, whether interacting in person or online.   CIG’s project leaders, meeting organizers, and committee and working group members are expected to act as representatives of CIG in carrying out their responsibilities.

CIG is dedicated to providing a harassment-free environment, regardless of gender, gender identity and expression, age, sexual orientation, disability, physical appearance, race, ethnicity, national origin, age, religion (or lack thereof), technology choices and experience level, or other group status.

Everyone taking part in CIG activities —speakers, helpers, organizers, and participants—is required to conform to the Code of Conduct throughout the activity.

Application Questions

In addition to basic contact and logistical questions, the questions below will help the hackathon organizers prepare instructional materials and assess the suitability of your proposed contribution.

 Graduate Student
 3 or more
 Not yet.
 Yes, I have used PyLith a little bit in my research.
 Yes, I have used PyLith on multiple research projects.
 No, I have only used the binary.
 Yes, I have built PyLith releases using the installer.
 Yes, I have built PyLith using the installer with source code from the Git repos.
 I am not familiar with the finite-element method.
 I learned about the finite-element method in a class but have not used it.
 I have used software that uses the finite-element method.
 I have written some simple finite-element method code.
 I have extensive experience writing finite-element code.
 I have only used binary packages.
 I have some experience creating Makefiles for compiling code.
 I have some experience installing software using configure, CMake, or other tools.
 I have some experience using autotools, CMake, or other tools to write build scripts for building software in a portable way.
 I have extensive experience using autotools, CMake, or other tools to write build scripts for building software in a portable way.
 I have not used a debugger.
 I have used a debugger a few times.
 I occasionally use a debugger.
 I use a debugger on a regular basis.
 I am not familiar with object-oriented programming.
 I have modified some simple programs that use object-oriented programming techniques.
 I have written some simple programs using object-oriented techniques.
 I have extensive experience using object-oriented programming techniques.
 I don't have any experience using Python.
 I have modified some Python code other people have written.
 I have used Python for some simple scripting.
 I have done some object-oriented programming with Python.
 I am extensive experience writing Python modules and interfacing them with low-level C or Fortran code.
 I am not familiar with C++.
 I modified some C++ code that others have written.
 I have written some simple C++ programs.
 I am very comfortable writing C++ programs using object-oriented programming.
 I have extensive experience writing C++ software using object-oriented programming techniques.
 I have not used LaTeX.
 I have used WYSIWYG interfaces for LaTeX, e.g., Lyx.
 I have modified some LaTeX documents.
 I am comfortable using LaTeX and have written some simple macros.
 I have experience creating style sheets, macros, etc in LaTeX.
 I have not used version control.
 I have used version control but not branches.
 I have used version control with branches.
 I have used version control with new features in separate branches.
 I have created and/or managed pull requests using Git.
 New 2-D reverse fault example suite
 New 2-D strike-slip fault example suite
 New 3-D strike-slip fault example suite
 Utility for adjusting mesh top surface to conform to topography/bathymetry
 Implement time-dependent Green's functions
 Implement point dislocation earthquake sources
 Implement poroelasticity material model
 Reformulate viscoelastic models to use strain rate rather than strain
 Importing MED mesh files from Gmsh, Salome
 Update PyLith to Python 3
 Workshop Fees*
Sign In