Code Monkey home page Code Monkey logo

whitakerlabprojectmanagement's Introduction

Whitaker Lab Project Management

Gitter

This repository contains issues related to the management of all Whitaker Lab projects along with weekly progress records for all lab members and collaborators.

Working open

At the Whitaker lab we are dedicated to working as openly as possible. We believe that our endeavors will be more successful through clear communication and collaboration than by keeping secrets. This repository is designed to showcase our "work in progress". You're welcome to help out along the way!

We may have private repositories if our collaborators are more comfortable with restricted working on some projects, but we aspire to "be the change" and demonstrate open working practices wherever possible.

Onboarding

If you're new to the lab, check out the Onboarding repository which will talk you through the different exercises and actions for your first few weeks in the lab.

Weekly updates

Lab members are asked to prepare for their regular meetings with Kirstie by completing their "Weekly-meetings" file and open a pull request to update the repository in advance of the meeting. You can find the public records of these meetings in the weekly-updates folder.

Lab meetings

Lab meetings are held every week on Thursdays at 3pm. Remote attendance is always supported. Participation (even if you can't attend the meeting itself) is required from all lab members. That means completing the three sections of the HackMD (attendance/apologies, something to share, a question to ask) in advance of the meeting, and ideally adding your comments to others' updates.

For a more detailed overview of the motivation and expectations for lab meetings see the lab onboarding repository.

You can see the schedule in the lab-meetings folder of this repository.

License and code of conduct

All content in this repository is openly licensed with a CC BY 4.0, which means you're free to use the materials and remix them so long as you credit the source.

For example, if you were to use content from this repo in your own project management lab guide, you'd attribute the Whitaker Lab with a sentence like:

The material in Dr. Mystery's Lab Guide is partially derived from "Whitaker Lab Project Management" by Dr. Kirstie Whitaker and the Whitaker Lab team, used under CC BY 4.0. Dr. Mystery's Lab Guide is licensed under CC BY 4.0 by [Your name here].

More on CC BY 4.0 licensing can be found at Creative Commons.

Our code of conduct requires that everyone who contributes to this repository is respectful of all members of the group. If you do not comply with the code of conduct, you will be asked to cease your participation in this collaborative project.

whitakerlabprojectmanagement's People

Contributors

aidamehonic avatar aldenc avatar amol-prabhu avatar arielle-bennett avatar arronlacey avatar awakenting avatar brainonsilicon avatar daniellecrobinson avatar dankessler avatar dingaaling avatar ekaroune avatar gedankenstuecke avatar georgiahca avatar giuliatomba avatar harisood avatar islast avatar ismael-kg avatar kirstiejane avatar lottycoupat avatar lzdh avatar malvikasharan avatar mariaeriksson avatar minnieho1115 avatar pherterich avatar sgibson91 avatar soledadli avatar sowmyaarajan avatar sparkler0323 avatar stephwright avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

whitakerlabprojectmanagement's Issues

Change license from MIT to CC-BY

Most of the information contained within this repository is documentation/curriculum resources rather than code so it makes more sense for us to use a CC-BY license rather than MIT.

The CC-BY license can be copied and pasted from here: https://choosealicense.com/licenses/cc-by-4.0/#

In order to complete the issue please first comment below to check that no one else is already working on the task. Then, once you're assigned: fork the repository, replace the text in the LICENSE file with the CC-BY text above, then submit a pull request!

This issue has been labelled as a good first bug. That means it is a particularly good place for new/nervous github contibutors to get started πŸ˜„

Research report for Turing

2-3 page report including:

  • The Turing research project or projects you have been working on since joining the Institute and any progress to date. Please also include the details of collaborations with other Turing researchers, connections/collaborations with Turing partners and any external collaborations.
  • The research you plan to undertake over the next 12-24 months, outlining how your research aligns to the Institute’s strategic priorities.
  • Publications that include acknowledgement of the Turing support.

Deadline 22nd August

Kirstie's TO DO list - week starting 17th July 2017

Emails/Online

  • Arrange meeting with HQ re: Turing policy work
  • Summary email from OpenConCam meeting
  • Follow up on open leadership materials for folk at OHBM
    • JS
    • EdP
  • Get business cards
    • Sharmila in charge for August
  • Read around Turing & brain for panel event - deadline 24th July
  • Accomodation & travel for ICON2017 - Amsterdam
  • Accomodation & travel for ECNP2017 - Paris
  • Travel for Mozilla - Toronto
  • Send Ed info on Impact Story

NSPN

  • Run longitudinal pipeline on HPHI
    • Need to be able to actually run code on HPHI first! See #39 πŸ˜•
    • Need to copy over the data from HPC
      • UPDATE 13/7: this is currently underway for UCHANGE directory
    • Also need to check that everything looks good
  • Write RA job description deadline 21st July
  • Update data management team on Cambridge repository
  • Download genetic data

Funding

  • Update reproducible research seed funding application deadline 18th July
    • KW: Sent to collaborators ⭐

Blogs/interviews/writing

  • 250 words on challenges & solutions for open science for OHBM Conversation piece deadline 25th July
  • Edit story engine for Mozilla
  • Blog telling people to apply for OpenCon, Moz Open Leadership & MozFest
  • Press release for Turing panel deadline 17th July

Invited talks

  • Bio/abstract for talk at EPFL library
  • Abstract & visa information for ICHBD
  • Make talk for ICON (and online brain intensive) - See #65

Peer reviews

  • A0028 deadline 17th July

Fragile Families

  • Send email about meeting on Wednesday
    • Didn't do πŸ™„ ...but could do for next week!

BrainAge

  • Get code installed & running
  • Send questions to FL

OpenAdvice

Kirstie's TO DO list - week starting 7th August 2017

URGENT

  • 250 words on challenges & solutions for open science for OHBM Conversation piece deadline 25th July
  • Letters of recommendation for SRA application deadline 26th July
  • Write RA job description deadline 21st July

To Do

Emails/Online

  • Arrange meeting with HQ re: Turing policy work
  • Send Ed info on Impact Story
  • Accept talk invite for SciData17
  • Send info on Turing event funding to CH
  • Review 50 OpenCon applications
    • 20/50 done πŸ™Œ 30/50 to go 😧
  • Email NCH re inclusivity call
  • Add ICON2017 slides to whitakerlab.github.io
  • Add quote to Mozilla retreat google doc
    "Why is Internet health such an important issue for humanity? Why do we each do this work? Why is it urgent?"
  • Feedback on OHBM Student/Postdoc SIG election docs
  • Edit IS email & report
  • Add links to Mozilla Science lab community call etherpad
  • MozFest wrangling - send email & join in process
  • Add bio to Mozilla retreat google doc
  • Bio, abstract, bank details for Lausanne summer school
  • Accomodation & travel for ECNP2017 - Paris
  • Email w interesting papers & links to Bullmore lab
  • Reply to PB email about outreach
  • Send link to KD re: impact podcast
  • Schedule meeting with CM

NSPN

  • Run longitudinal pipeline on HPHI
    • Need to be able to actually run code on HPHI first! See #39 πŸ˜•
    • Need to copy over the data from HPC
      • UPDATE 13/7: this is currently underway for UCHANGE directory
    • Also need to check that everything looks good
  • Incorporate von Economo atlas in NSPN code
  • Send HCP parcellation data to JS deadline 1st August
  • Update data management team on Cambridge repository
  • Email to SW & PV re analysis update
  • Upload data for BK's paper
  • Arrange date for next data management meeting

Blogs/interviews/writing

  • Edit story engine for Mozilla

Invited talks

  • Talk for brainintensive -- see #65
  • Bio/abstract for talk at EPFL library

Fragile Families

  • Send email about close of competition

BrainAge

  • Get code installed & running
  • Send questions to FL

OpenAdvice

OpenConCam

  • Summary email from OpenConCam meeting & voting on speakers
  • Update OpenConCam website w save the date details
    Added issue OpenConCam/issues/20

Peer Reviews

  • A0029 deadline August 29th
  • A0030 deadline August 30th

MozFest

  • Read through spreadsheet & categorise
  • TheGamma

Kirstie's TO DO list - week starting 31st July 2017

URGENT

  • 250 words on challenges & solutions for open science for OHBM Conversation piece deadline 25th July
  • Bio/abstract for talk at EPFL library
  • Summary email from OpenConCam meeting & voting on speakers
  • Talk for ICON -- see #65

To Do

Emails/Online

  • Arrange meeting with HQ re: Turing policy work
  • Accomodation & travel for ECNP2017 - Paris
  • Send Ed info on Impact Story
  • Letters of recommendation for SRA application deadline 26th July
  • Arrange meeting with Ed, SW & PV for August
  • Arrange meeting w PV for August 3rd
  • Accept talk invite for SciData17
  • Email w interesting papers & links to Bullmore lab
  • Send info on Turing event funding to CH
  • Review 50 OpenCon applications
    • 10/50 done πŸ™Œ 40/50 to go 😧
  • Email NCH re inclusivity call

NSPN

  • Run longitudinal pipeline on HPHI
    • Need to be able to actually run code on HPHI first! See #39 πŸ˜•
    • Need to copy over the data from HPC
      • UPDATE 13/7: this is currently underway for UCHANGE directory
    • Also need to check that everything looks good
  • Incorporate von Economo atlas in NSPN code
  • Send HCP parcellation data to JS deadline 1st August
  • Write RA job description deadline 21st July
  • Update data management team on Cambridge repository
  • Email to SW & PV re analysis update

Blogs/interviews/writing

  • Edit story engine for Mozilla
  • Blog telling people to apply for OpenCon, Moz Open Leadership & MozFest
    • sigh didn't end up doing 😭

Invited talks

Applications

  • MozFest
    • Building an open research culture at the Turing
    • OpenAdvice
  • MozFest & Moz Open Leaders
    • Feedback to EC
    • Feedback to IS
    • Feedback to SH
    • Feedback to HumanityX
    • Feedback to RL
  • OpenCon
    • Feedback to SH
    • Feedback to IS
    • Own application

Fragile Families

  • Send email about close of competition

BrainAge

  • Get code installed & running
  • Send questions to FL

OpenAdvice

OpenConCam

Roadmap

This roadmap will guide you through the various actions that are currently on the to do list for the Whitaker Lab. It's very similar to the project management board.

Updated on 10th May 2017

Lab management

  • Set up onboarding repository #2
    • Weekly meeting template #13 DONE πŸŽ‰
    • Write open science primer into reading list #11 DONE πŸŽ‰
    • Develop introduction to MRI reading list #14
  • Build lab website #3 DONE πŸŽ‰

Learning brain network analysis

  • Set up tutorial to learn network analysis in python

General admin

  • Kirstie's TO DO week starting 8th May: #18

Process Cambridge MRI data

Studies

  • UCHANGE
  • NCAAPS
  • CLINICAL_PILOT
  • MRIMPACT
  • GAP_STUDY
  • AVOIDANT_OCD

Timepoints:

  • baseline
  • 6_month
  • 1st_follow_up

Kirstie's TO DO list - week starting 24th July 2017

Emails/Online

  • Arrange meeting with HQ re: Turing policy work
  • Read around Turing & brain for panel event - deadline 24th July
  • Accomodation & travel for ICON2017 - Amsterdam
  • Accomodation & travel for ECNP2017 - Paris
  • Send Ed info on Impact Story
  • Info to OHBM student/postdoc SIG
  • Letters of recommendation for SRA application deadline 26th July
  • Register for Cam Neural Networks & promote at Turing

NSPN

  • Run longitudinal pipeline on HPHI
    • Need to be able to actually run code on HPHI first! See #39 πŸ˜•
    • Need to copy over the data from HPC
      • UPDATE 13/7: this is currently underway for UCHANGE directory
    • Also need to check that everything looks good
  • Write RA job description deadline 21st July
  • Update data management team on Cambridge repository

Blogs/interviews/writing

  • 250 words on challenges & solutions for open science for OHBM Conversation piece deadline 25th July
  • Edit story engine for Mozilla
  • Blog telling people to apply for OpenCon, Moz Open Leadership & MozFest

Invited talks

  • Bio/abstract for talk at EPFL library
  • Abstract & visa information for ICHBD
  • Make talk for ICON (and online brain intensive) - See #65

Fragile Families

  • Send email about meeting on Wednesday
    • Didn't do πŸ™„ ...but could do for next week!

BrainAge

  • Get code installed & running
  • Send questions to FL

OpenAdvice

OpenConCam

Write up how to guide for HPHI

This could potentially be a protocols.io guide.

Apply for an account

  1. Apply for an HPHI account.

    ⏲ wait for account to be created

Download and setup the required software

  1. Download X2Go client & Putty
  2. Set up a connection to the Cambridge VPN service
    Choose the operating system you use (eg Windows 10, OS X Sierra etc) from the links on the left side of that page to find the specific instructions for your device.

Connect

  1. Connect (either via X2Go, or Putty) to wbic-gate.vss.cloud.private.cam.ac.uk
    Check out the pictures at this help page to make sure you get all the right checkboxes filled in!

Kirstie's TO DO list - week starting 10th July 2017

Emails/Online

  • Arrange meeting with HQ re: Turing policy work
  • Summary email from OpenConCam meeting
  • Follow up on open leadership materials for folk at OHBM
    • JS
    • EdP
  • Send email introducing SF to TR group
  • Send email w pre-registration info to SH
  • Reply to email Q about PNAS analysis

NSPN

  • Update SW & PV on work so far
  • Run longitudinal pipeline on HPHI
    • Need to be able to actually run code on HPHI first! See #39 πŸ˜•
    • Need to copy over the data from HPC
      • UPDATE 13/7: this is currently underway for UCHANGE directory
    • Also need to check that everything looks good

Blogs/interviews/writing

  • 250 words on challenges & solutions for open science for OHBM Conversation piece deadline 25th July

Invited talks

  • Bio/abstract for talk at EPFL library
  • Abstract & visa information for ICHBD

OpenAdvice

Peer reviews

  • A0027 deadline 9th July
  • A0020 deadline 10th July
  • A0028 deadline 17th July

Blog about code exercise

Hi @Islast - I've made a little description of the blog about some code exercise.

I don't think this should be rushed so I've suggested a 2 week deadline - 26th May. Don't worry if that is unreasonable, lets just revisit where you're at when we can πŸ˜„

Run structural covariance network analysis on PNAS data

You can find the original data in the WhitakerVertes GitHub repository:

You can find the code to run the analyses in the BrainNetworksInPython repository. Please fork that repo and update any of the code as needed!

  1. Make a structural covariance network
  2. Calculate global and nodal measures for this network at a couple of different costs
  3. (Stretch goal) visualise these outputs

Please write up some documentation (in this repository's wiki page) along the way to make this experience easier for the next person!

In particular, please create a wiki page on "getting started" that explains which python libraries are necessary to install.

Add example attribution sentence to the README

There have been some great comments on twitter about the Whitaker Lab CODE_OF_CONDUCT.md and requests to use the text for other groups/projects.

As part of the mozilla global sprint (#mozsprint πŸ™Œ ) @stephwright changed the LICENSE from MIT to CC-BY (PR #44) which makes much more sense as almost everything in this repository is text rather than software.

The next step is to add a sample sentence to the README file to make it super easy for anyone who does use materials from this repository to attribute the source πŸ˜„.

If anyone wants to give this a whirl you're super welcome. Please comment on the issue to make sure that no one else is already working on it. Once you get the go ahead fork the repository and add an example sentence to the README in the License and code of conduct section. Then submit a pull request and ask @KirstieJane to review πŸ˜€ .

Kirstie's TO DO list - weeks starting 19th & 26th June 2017

Emailing/Online

  • Add Maria to Fragile Families GitHub
  • Make schedule for OHBM (download app)
  • Write up instructions for tweeting for OHBM trainees during conference - see #56
  • Arrange final chat with Open Leadership mentees
  • Expenses for Mozilla
    • Vaccinations
    • Laptop
    • Text book
    • Ubers?
    • Dinners in Cape Town
  • Send data around to mozfellows to figure out fun finances
  • Add US travel to mozilla spreadsheet
  • Update CV & mozilla resume with great bio
  • Reply to Z re working in the lab
  • Reply to J re working in the lab
  • Congratulations email to JS
  • Review event proposals - see #58 deadline 26th June

Whitaker Lab

  • Isla blog feedback

NSPN

  • Data to PV
  • Reviewer feedback to FV
  • Comments to RRG

Peer reviews

  • A0026 deadline 2nd July
  • A0027 deadline 9th July
  • A0020 deadline 10th July

Create myelin reading list

Inspired by the Exploring the future of myelin research in Cambridge workshop on May 11th, I decided to make a reading list for anyone interested in myelin.

(Although, it will almost certainly have a developmental and plasticity bias - I know there are so many more ways to think about myelin degeneration).

Please add your favourite papers below and I'll incorporate them asap πŸ˜„

Onset of mental health disorders: https://www.ncbi.nlm.nih.gov/pubmed/15939837

Kirstie's TO DO list - week starting 15th May 2017

Emailing/online

  • Set up site for Mozilla Global sprint in SF Mountain View
    • Register and promote
  • Reach out to internship supervisors re: microWOW for interns
    • Send 2-3 sentence description and title to Emma & Emily
  • Apply for data for the fragile families challenge
    • Send out email about meeting on Wednesday
  • Upload code & data to Cambridge repository
    • Rogier
    • Anne-Laura
  • Book travel & accommodation
    • Lon to SF
    • LA to CT
    • CT to YVR
    • YVR to Lon
  • Send in paperwork for OHBM travel award
  • Find time to chat w LC from OpenCon
  • Find time for OHBM SIG meeting
  • Expenses for Mozilla - travel to Penn, microWOW and laptop
  • Book OpenConCam meeting for 23rd May and first tuesday of the month til December
  • Register for ICON
  • Bio for Gay UK event
  • Travel award paperwork for OHBM hackathon
  • Book flights for Lausanne trip

In person

  • Drop off cash for retirement & sign card

Peer reviews

  • A0025

Presentations

  • Poster for Cam BrainFest - see #23
  • Talk for Biological Psychiatry conf

Blogs

WOW

  • Build up WOW for Amsterdam, Turing and OHBM Brainhack

NSPN Data Sharing

  • Write up documentation for how to access data from NSPN paper
  • Get information up on NSPNTeam repository

Data wrangling

  • Update table of participants for NSPN & assoc studies
  • Process all scans - see #17
  • Wrangle data into a nicer format - see #22

OpenConCam

Applications

Kirstie's TO DO list - week starting 3rd July 2017

Online/emails etc

  • Send doodle for SIG meeting
  • Complete feedback for SIG meeting
  • Submit Mozilla expenses deadline 6th July
  • Coordinate meeting w B & I
  • Figure out job submission requirements for HPHI - see #39
  • Bio, abstract, title for Lausanne evening talk
  • Bio for Alan Turing evening at BL

NSPN

NORA

  • Upload filtered_func_data.nii.gz & send info to meta analysis inquiry

Peer reviews

  • A0026 deadline 2nd July
  • A0027 deadline 9th July
  • A0020 deadline 10th July
  • A0028 deadline 17th July

Workshops/teaching

  • Update github teaching materials for workshop at Turing deadline 3rd July
  • Send email to turing interns about revert command missing from github desktop

Kirstie's TO DO list - week starting 8th May 2017

Emailing/online

  • Send back COI for Bea's paper
  • Submit MPhil feedback
  • Set up site for Mozilla Global sprint in SF
  • Give feedback on fellowship application
  • Reply to summer school invite
  • Reach out to internship supervisors re: microWOW for interns
    • Send 2-3 sentence description and title to Emma & Emily
  • Recruit more submissions for gift
  • Apply for data for the fragile families challenge
  • Upload RK's code & data to Cambridge repository
  • Find code for visualising behavioural networks
  • Feedback for K's application
  • Feedback on Bruno's blog post
  • Book travel & accommodation
    • Lon to SF
    • LA to CT
    • CT to YVR
    • YVR to Lon
  • Find time to chat w LC from OpenCon
  • Find time for OHBM SIG meeting
  • Register for Biological Psychiatry conference
  • Feedback on Bruno's blog post
  • Feedback on K's application

In person

  • Drop off cash for retirement & sign card

Peer reviews

  • A0024
  • A0025

Presentations

  • Poster for Cam BrainFest - see #23
  • Talk for Biological Psychiatry conf

Blogs

Documentation

  • Write up documentation for how to access data from NSPN paper

Data wrangling

  • Update table of participants for NSPN & assoc studies
  • Process all scans - see #17
  • Wrangle data into a nicer format - see #22

OpenConCam

Develop the introduction to MRI reading list

I (Kirstie) have really deep expert blindness when it comes to remembering how I learned about MRI (it was in 2007 at 8am every Wednesday morning at UBC in Vancouver!

This is a really tough request, but I'd like you to build up some useful resources for understanding how we use MRI for neuroimaging.

Some guidelines:

  1. You don't need to know everything at the deepest level! There are some really great youtube videos or blog posts that will talk you through conceptually how MRI can be used to image the brain. I'd recommend starting with them before jumping into a pubmed search.

  2. On the other hand you aren't the first person to have to learn how MRI works! There are probably some really useful introduction/overview papers that you can find. Try searching pubmed for review papers only...or follow links from the blogs and videos etc.

  3. You can learn iteratively! You don't have to understand everything you read the first time through. If it's written in a way that you feel you might like to come back to, keep the link, add a little sentence about it to the reading list and keep going on your quest.

You got this!

Make guidelines for conference tweeting

This is specifically for tweets coming from the OHBM trainees account at the 2017 conference in Vancouver.

BUT - it doesn't have to be so specific. I think a little blog post (maybe in resources section) on things to consider for anyone who manages a shared twitter account would be a useful thing to create πŸ˜„

Here's my brainstorming from chatting with @teonbrooks:

WHY are you tweeting?

Have a deep thing about why you want to tweet. What are your goals? Why not just tweet from your own account?

There's no right or wrong answer here, but making sure that everyone in the team you're representing agree on why you're putting this effort in will go a huge way towards avoiding any miscommunications πŸ™Œ

If in doubt, be nice

It's probably a bad idea to critisise from a shared account (unless this is one of your goals, in which case go for it!) so I'd recommend defaulting to positive tweets.

If in doubt, you can always switch to your personal twitter account and comment more candidly there.

Use the hashtag & thread where possible

Make sure you're using the event hashtag in as many of your tweets as possible. That's a key way that others from outside of the event are going to be able to find and follow you.

Threading tweets allows tweets to be linked together, whether

Humanise the thread

This is highly related to the point above about why are your tweeting. It is easier to engage people when they feel like they're talking with a real human being. Consider adding the twitter handle of the people tweeting from the account in the bio.

If there are multiple people tweeting you could ask members of the team to signing your tweets. It might be difficult to remember to sign every tweet, so a suggestion is to focus on remembering to sign the first in a thread rather than every one of them.

Promoting work

If you're at a conference you might want to promote the people and the work that is being presented. Tagging the speaker if they're on twitter makes sense and lets people follow up with questions. You could take a picture during the talk, but make sure to check whether the speaker or conference organisers have a policy forbidding public discemination of the work presented.

Kirstie's TO DO list - week starting 22nd May 2017

Emailing/online

  • Reach out to internship supervisors re: microWOW for interns
    • Send 2-3 sentence description and title to Emma & Emily
  • Apply for data for the fragile families challenge
    • Send out email about meeting on Wednesday
    • Fragile families email to team re meetings in June and July
  • Upload code & data to Cambridge repository
    • Rogier
    • Anne-Laura
  • Book/organise accommodation
    • SF/Berkeley/Mountain View
    • Cape Town
    • Vancouver
  • Find time to chat w LC from OpenCon
  • Expenses for Mozilla - travel to Penn, microWOW and laptop, airbnb in Mountain View
  • Email abstract for talk at Stanford
  • Email AG w info on visit
  • Email BIDS re visit
  • Email CM re visit
  • Review IS pull request - see #19
  • Send mentoring resources to MV

In person

  • Drop off cash for retirement & sign card

Peer reviews

  • A0025

Presentations

  • Poster for Cam BrainFest - see #23
  • Talk for visit to Poldrack lab

Blogs

WOW

  • Build up WOW for Amsterdam, Turing and OHBM Brainhack

NSPN Data Sharing

  • Write up documentation for how to access data from NSPN paper
  • Get information up on NSPNTeam repository

Data wrangling

  • Update table of participants for NSPN & assoc studies
  • Process all scans - see #17
  • Wrangle data into a nicer format - see #22

OpenConCam

Applications

Kirstie's TO DO list - week starting 29th May 2017

Emailing/online

  • Reach out to internship supervisors re: microWOW for interns
    • Send outline of schedule to Emma & Emily
  • Fragile families email to team re meetings in June and July
  • Upload code & data to Cambridge repository
    • Rogier
    • Anne-Laura
  • Book/organise accommodation
    • Cape Town
    • Vancouver
  • Find time to chat w LC from OpenCon
  • Expenses for Mozilla - travel to Penn, microWOW and laptop, airbnb in Mountain View
  • Email AG & ??? w info on visit to Stanford
  • Review IS blog post - see whitakerlab.github.io #15
  • Add seaborn info to IS visualisation issue - see #19
  • Introduce IS and MOR re testing
  • Email Antonia
  • Slack w MOR & JH re seed funding
  • Email paper on freesurfer to SM
  • Thank stem cell team re brainfest

Presentations

  • Poster for Cam BrainFest - see #23
  • Talk for visit to Poldrack lab

Blogs

WOW

  • Build up WOW for Amsterdam, Turing and OHBM Brainhack

NSPN Data Sharing

  • Follow up with repository re: data access
  • Figure out what's needed for PI meeting

Data wrangling

  • Update table of participants for NSPN & assoc studies
  • Process all scans - see #17
  • Wrangle data into a nicer format - see #22

OpenConCam

Applications

Make brain development poster for Cam Brain Fest

Brief: Discuss human brain development - what we can see at different ages and how we care about brain structural changes during adolescence.

Panels to include:

  • Measuring myelin in cortex - including video
  • Measuring how myelin changes during adolesence - inc video
  • Some pictures of brains at different ages - eg: 4, 7, 10, 14, 20?
    • Point being that you can't see huge changes all the way through...but you can when you look carefully
  • Talk to Ursula in Mackey lab about making some beautiful pictures from PING?

Also need to check about following up with the stem cell group

Meeting people at the Turing blog

@Islast - I know you're already working on this, I just wanted to make an issue because I really enjoy closing them when they're done.

You can also use this issue to ask me any questions you have about formatting the blog post etc. If you'd like, I'm happy to do the fiddling around to make it look pretty πŸ˜„

NSPN MRI Report

From email:

Make a summary document about what U-Change MRI data was collected and what state it’s in.
Summarise what has happened to the data since – what processing has been used, have any been written off as unusable, that sort of thing?

See attachment from LV in email.

Build template for weekly meetings

Each weekly meeting should cross off a few different topics:

  • Who did you help this week?
  • Who helped you this week?
  • What did you achieve?
  • What did you struggle with?
  • What would you like to work on next week?
  • Where do you need help from Kirstie?
  • Any other topics

Need to add this template to the onboarding documentation πŸ˜„

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.