|
Size: 11334
Comment:
|
Size: 11355
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| Line 10: | Line 11: |
| 3 : Remove dismissive prefacing statements (Ex : "How could they possibly think..", "Everyone should have learned this in grade school, undergrad, grad school, when they were in the womb", "Here's a stupid/dumb question" | 3 : Remove dismissive prefacing statements (Ex : "How could they possibly think..", "Everyone should have learned this in grade school, undergrad, grad school, when they were in the womb", "Here's a stupid/dumb question" ) Who needs em? |
| Line 12: | Line 15: |
| Line 20: | Line 24: |
The LIGO journal club usually meets at 3:00PM on Fridays on 2nd floor of W Bridge (room 265). During the summer we will meet in room 351 in W. Bridge. We meet to discuss a recent journal article from PRL, ApJ or the like. Someone is designated as a lead, to initiate the discussion, but not to present slides or give a monologue. The lead should also post a link to the article the Tuesday before meeting in the Meetings and papers section below.
Preferably, selected articles won't be exceptionally long, and would relate (at least tangentially) to LIGO.
You will be emailed by the journal club Tsar two weeks out from your date and again a week out. The rotating roster can be found at HERE
Community Agreements
1 : Every questions is a valuable question
2 : Use "I" statements (ex : "Here's how I understand it" or "My thoughts are..."
3 : Remove dismissive prefacing statements (Ex : "How could they possibly think..", "Everyone should have learned this in grade school, undergrad, grad school, when they were in the womb", "Here's a stupid/dumb question" ) Who needs em?
4 : Work to find an explanation that brings everyone on to the same page. Our colleagues are theorists, data analysts, experimentalists and may not be familiar with jargon from the other worlds or remember some random term from undergrad. And that's okay.
5 : Make space, take space. (If you speak up a lot, maybe sometimes take a step back. If you don't speak up a bunch then practice stepping in)
Mailing List
Send emails to everyone: ligo-journal-club@caltech.edu
Click here to subscribe
Highlighted papers pool
If we are short of a presenter we will draw something from this list of papers. If find any papers that would be interesting to discuss at future journal club meetings, then you should add them to the list on the following page:
Older papers on this list can be found in the Interesting papers (archive) page.
Meetings and papers
Date |
Lead |
Link (pre-print or other open format) and other links |
Link (official DOI peer reviewed version) |
Attendance |
Journal club roster 2017
You can find an ordered list of upcoming presenters HERE. The JCTsar script will chose people in this order.
If you find you can't do a week that you are assigned to then find someone willing to trade and update that spreadsheet.
Chooser script (Updated python)
https://github.com/fincle/RoboTsar
The python script TsarMailer.py downloads the google spreadsheet list. This sheet contains an ordered list of names and a list of public holidays to veto. It counts the number of days since the start of the year, vetoing public holidays and chooses presenters sequentially from the list. The scripts loops back to the beginning once the end is reached. An arbitrary phase shift is also added to the week number so that the list position can be twiddled in the event the presenter list length changes and position needs to be fixed.
If a swap of names is performed leaving the list length the same there is no need to adjust the phase factor.
Three other scripts exist to remind the presenter to post a paper and to remind people on the day.