Institute/Group Workshops (typically weekly)
(For ANC this is Tues 11-12. Other institutes/groups etc. will have their own equivalents). This is typcially a chance to present your work to an appropriate audience, very much as you might to a broad (e.g. plenary) conference audience.

PIGS (Fortnightly)
This is a paper discussion meeting, loosely scheduled for 1 hour, (1.5 hours maximum). The idea is that one person is responsible for choosing and introducing a research paper or couple of conference papers, and promoting discussion on the paper(s). But note that they are not presenting the paper; it is a paper discussion and it is expected that everyone will have read the paper ahead of time (unless otherwise advertised). This is for all PIGS members.

PIGlets (Fortnightly)
This is a paper discussion meeting for PhD's and postdocs, with a focus more on tutorials and getting a background in a subject. (Others may attend as invited or on occasion, but if so, more senior members should try to keep quiet unless absolutely necessary to allow the more junior members to contribute smile ).

Brainstorm Coffee (weekly)
This meeting starts promptly at 10:30, and is scheduled ideally for 20 minutes, but with a strict maximum of 30 minutes. The idea is that this should be a minimal time commitment to encourage everyone to attend even if it may be a bit tangential. The point of this meeting is to present a self contained (but open ended) problem for discussion. The purpose is to promote collaboration, get leads on an area of work, to lead to publication or to prevent wasted time by a (brief) application of pooled knowledge. It also gives a chance to promote discussion of those things you wouldn't get away with talking about in any other setting :). Make it a discussion rather than a talk.

This meeting is harder to characterise. As it may be hard to see what this means, I'll elaborate as it is helpful to have some pointers when your turn to present comes up.

The focus of discussion in Brainstorm Coffee is often on the problem or observation rather than your solution, though it is common to present how you might choose to go about tackling the problem. Talks presenting your general current technical issues at this stage of your PhD are not recommended (there is usually too much background and too little opportunity for others to be involved). On the other hand, taking a particular issue you may be currently facing and presenting that specific problem in a slightly more self-contained context is very valid. So is talking about a specific idea completely unrelated to your main line of work. So is posing a particular technical question, so long as you can motivate its wider applicability. So is presenting others work, or others data, if you think there are interesting potential discussions around it. The ideas and thoughts are likely to be rough around the edges or turn out to be potentially flawed. That's okay. In summary, if it can be introduced briefly to a technically competent audience, may potentially capture the interest of others, and it leaves room for discussion then that's great!

This is an informal talk setting. Keep it short and do not use it as an excuse to generally present your work (there isn't time for that). Also be aware that people may not want ideas/problems presented here communicated by others to a wider audience.

-- AmosStorkey - 17 Sep 2010

Topic revision: r5 - 10 Oct 2016 - 12:41:46 - AmosStorkey
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies