geoschem / geos-chem-cloud

Run GEOS-Chem easily on AWS cloud
http://cloud.geos-chem.org
MIT License
39 stars 9 forks source link

IGC9 AWS workshop instructions and user feedback form #24

Closed JiaweiZhuang closed 4 years ago

JiaweiZhuang commented 5 years ago

Basic workshop information

Time: Thursday (05/09), 3:00-5:00 pm Location: Maxwell-Dworkin G115 Requirement: Bring a laptop with internet connection. To connect to WIFI, follow Connect to Harvard Wireless as a guest, "Connecting to Harvard wireless as a visitor" (second section).

Free temporary AWS accounts will be provided during the workshop. We have 30+ registered participants right now and can accommodate at most 40 people.

Optional preparations

Here are the preparations you can do before the workshop. You don't have to do any of those before coming, and can instead do those during the workshop. But those steps can help you get most out of the workshop (so you can spend less time waiting for software installations, etc.)

  1. Sign-up for a GitHub account at https://github.com/join. You will need such an account to provide workshop feedbacks (detailed later). You can further use the account to ask questions and report bugs about GEOSChem-on-cloud, on the GitHub issue tracker. Treat it as an online forum. GitHub is also the currently recommended way to submit your code updates, so it is nice to have an account, anyway. Finally, consider giving a star to the repositories under the GEOS-Chem team. Just click on the "star" button on the upper-right corner of each repository page. This "shows appreciation to the repository maintainer for their work".

  2. Study our Python tutorial at https://github.com/geoschem/GEOSChem-python-tutorial, if you have no Python experience before. The workshop will involve a little bit of Python. But it is also fine to come without prior knowledge.

  3. For Windows users, install Git-Bash as a Linux-like terminal. This is mentioned in more detail in our online guide:

On Windows, I highly recommend installing Git-BASH to emulate a Linux terminal, so you can follow exactly the same steps as on Mac/Linux. Simply accept all default options during installation, as the goal here is just to use Bash, not Git. Alternatively, you can use MobaXterm, Putty, Linux Subsystem or PowerShell with OpenSSH. But the Git-BASH solution should be the most painless and will also work smoothly in later steps where we add port-forwarding options to connect to Jupyter.

Tutorial contents used for the workshop

You will follow the comprehensive online tutorials at http://cloud.geos-chem.org. Due to time constraints, the workshop will only cover two essential parts:

The slides used for Thursday morning's model clinic are also available here, as a summary for the online tutorial.

Reply your feedbacks here!

You will reply to this survey by simply posting comments within this GitHub issue (i.e. the current page you are looking at). See the "comment" cell at the bottom of this page, with a big, green "comment" button (need to login to GitHub first).

  1. Background: Your university name and how long have you been using GEOS-Chem.
  2. Time to finish the EC2 part (Part 1). You may do a rigorous timing, but just a rough number is good enough, such as 30 minutes or 60 minutes.
  3. Time to finish the S3 part (Part 2). Again a rough number is good enough.
  4. General comments, if any. (e.g. unclear documentations, confusing web console)
  5. Are you planning to use cloud computing for your research? If not, what's your concern (e.g. cost, funding, docs, learning curve, already have compute resources, etc)?

To get a feeling of how the replies would look like, see out past survey at #15. All replies under this issue should adhere to the above user-feedback format. For general discussions on workshop plans, please comment under #23.

JiaweiZhuang commented 5 years ago

Here's a sample reply:

Background: XX University, X years of GEOS-Chem experience Time to finish the EC2 part: X minutes Time to finish the S3 part: X minutes General comments: None Whether to use cloud computing for research: Yes/No/not-sure

nairarshad commented 5 years ago

Background: SUNY-Albany, 2 years of GEOS-Chem experience Time to finish the EC2 part: 20 minutes Time to finish the S3 part: 30 minutes General comments: Clear documentation makes this easy to use. Whether to use cloud computing for research: Yes

yiqi0813 commented 5 years ago

Background: MIT, 2 months of GEOS-Chem experience Time to finish the EC2 part: 15 minutes Time to finish the S3 part: 25 minutes General comments: Clear instruction step by step. Whether to use cloud computing for research: Yes

Jun-Meng commented 5 years ago

Background: Dal, 2 years of GEOS-Chem experience Time to finish the EC2 part: 20 minutes Time to finish the S3 part: 30 minutes General comments: Clear documentation. Whether to use cloud computing for research: not sure

jingli0714 commented 5 years ago

Background: Harvard, no GEOS-Chem experience Time to finish the EC2 part: 25 minutes Time to finish the S3 part: 20 minutes General comments: None. Whether to use cloud computing for research: not sure

xin-chen-github commented 5 years ago

Background: U. Minnesota, 6 years of GEOS-Chem experience Time to finish the EC2 part: 20 minutes Time to finish the S3 part: n/a General comments: None Whether to use cloud computing for research: not-sure

mariazatko commented 5 years ago

Background: 9 years of GEOS-Chem experience (U. Washington PhD now at Ramboll) Time to finish the EC2 part: 30 minutes Time to finish the S3 part: N/A General comments: Great workshop! Well done! Whether to use cloud computing for research: Definitely

GongdaLu commented 5 years ago

Background: U of Birmingham (UK), 0.5 years of GEOS-Chem experience Time to finish the EC2 part: 20 minutes Time to finish the S3 part: 30 minutes General comments: 1> Great step-by-step tutorial! I will surely recommend this to other students. 2> GC on AWS is really cool and easy to use! Whether to use cloud computing for research: not-sure (funding is key)

yantosca commented 4 years ago

We can close out this issue, as it is more than 2 years old.