Dario Pescini
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    OLS-4 Meeting Minutes Template: <Nadine + Dario> === ###### tags: `mentor-mentee meeting` `OLS-4` ==This is a Template only. Please copy the text provided here to create a shared document for your mentee-mentor meeting. For example, you can use a shared Google document, HackMD, or any other online documentation tool/services. Use the weekly format as guides and make update it to fit your meeting or project requirements. Please contact the Open Life Science team for any help: [team@openlifesci.org](mailto:team@openlifesci.org)== :::info - **Call time**: Friday 10:30 CEST - **Project name**: [Writing a Python library for measures of complexity & emergence] - **Project lead(s)**: [Nadine Spychala] - **Mentor(s)**: Dario Pescini - **Call joining link**: [https://universityofsussex.zoom.us/j/98945507506, Meeting ID: 989 4550 7506] (e.g. Zoom, hangouts). (Agree on this during/before your first meeting!, see details here: https://openlifesci.org/ols-4#resources) ::: **Table of content** [TOC] ## Week 0 - Please read the email sent by OLS organisers to you - Create a [GitHub account](https://github.com/) if you don't have one already - you will need that to login to HackMD and edit this document - Get started with HackMD using this short guide: https://hackmd.io/@openlifesci/OLS-HackMD-guide **Preferred time and days provided by the project lead(s)** - We have the following information from the project leads (you can make changes as needed so that your mentor can identify the most suitable time for your intro call with them): ### Homework before meeting your mentor **Project Lead (mentee) will:** 1. Take a Self-Assessment [SURVEY](https://docs.google.com/document/d/1wJWvgHxAsQkf_kuM7AKXPr3lxw-_Yr5JUge73d5Zpq4/edit?usp=sharing) and share the outcome with their mentors during the call. - [Link to your notes from the survey outcome] 2. Based on the insights gained from the survey, set 1-2 personal open science goals for yourself in OLS (it doesn't have to be about your project). - [Add your response here] 3. State how their mentors can best support them in OLS (providing accountability, connect them with right people, share useful resources, specific skill they can help them gain either directly or with the help of OLS experts) - [This could be a copy of what you wrote in your application] ## Week 1 **Roll call** - - **Attendees** - - ### Agenda and Notes for Week-1 - Introductions - get to know each other - [TAKE NOTES HERE] - Mentees, tell your mentor about yourself - [TAKE NOTES HERE] - Set your overall goals for your project - [TAKE NOTES HERE] - Where do you want your project to be by the end of the program (in 15 weeks)? Possible areas to think about: - Community: Contributors / Maintainers / Members - Product (Launch / MVP / Feature) - Resources / Sustainability (Governance / Funding / Gifts) - [TAKE NOTES HERE] - Mentees, discuss your notes from your homework **Meeting logistics & Reminders** - Does this time every 2 weeks work for everyone? - Full cohort call next week (see Syllabus for details: https://openlifesci.org/ols-4) **Assignments after this call** - Draft a brief **vision statement** using your personal and project goals. Please [use this document as guide for this assignment](https://docs.google.com/document/d/1rkWI7F-XBYjEeyRHNyGNaG7Qth6T_tNvlzXMEjpp4nk/edit). - You might address: - The problem you’re trying to solve. - How you think openness and open leadership will help solve it. - How meeting your personal goals will help you and help solve the problem. - How meeting your cultural goals for your community, organization, or project will help solve the problem. - Add your vision statement to your repo by uploading it or copy and pasting it into your README document. - Anything else? *Follow this [chapter from the Open Leadership Training Series (OLTS)](https://mozilla.github.io/open-leadership-training-series/articles/introduction-to-open-leadership/stating-your-project-vision/) to create your vision statement.* ## Week 2 **Notes from the mentor-mentee meeting (24th Sep 2021)** 1. Papers about the measures of emergence I am implementing: a) Dynamical independence: https://arxiv.org/abs/2106.06511 b) Causal emergence: https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1008289 2. link to github issue with my project: https://github.com/open-life-science/ols-4/issues/13 ## Week 3 - Agenda: https://openlifesci.org/ols-4/schedule/#week-03 **Roll call** - - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-04 **Links to your assignments to share with your mentor** ADD LINKS TO YOUR ASSIGNMENTS MENTIONED IN THE LAST COHORT CALL - Open an issue on ols-4 repo where you will be able to track you progress in this cohort: https://github.com/open-life-science/ols-4 - Complete the compare and contrast assignment about current and desired community interactions and value exchanges. - Start working on your Open Canvas ([instructions](https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/develop-an-open-project-strategy-with-open-canvas/), canvas) - Reflection exercise on your role as a mentee and a project leader in ols-4 ### Agenda and Notes - Establish a check-in ritual and try it. (2-3 minutes) (Examples: weather check (my project feels like a blustery wind right now), .gif share, video share) - weather-project comparison (tell something about the eather and how it compares to the project) - it shines on the project: oct2py now works, it is possible to see faraway to move away from it in the future - Establish a culture of gratitude ritual (if you have not already). (2-3 minutes) (Examples: recognitions (recognize colleagues), sparkling moments (recognize community members), shout-outs) - people who helped - significant other has helped in my oct2py() problem - my family supporting me in hard working (d) - Review your goals and any progress you’ve made towards them. Any challenges to mention? (5 minutes) - solving oct2py() problem which lets me move on with further writing the library - challenge: having a very generic error feedback and trying to find the solution with that - Review your assignments from last week, reflect on where in your project are they applicable. (10 minutes) - (your notes) - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - (your notes) - Discuss if your mentor should help identify experts to invite to one of the future mentor meetings (2-3 minutes). - Use these question to brainstorm this section: Do we need an expert at any stage? Which week they might likely be useful? Which area do we need expert advice? - will think about that! - Anything else: - (your notes) ### After this call **Next week: Cohort call** - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-04 **Assignments before the next cohort call** 1. Share the image/link on your GitHub issue 2. Look up at least two other projects in the issues and comment on their issues with feedback on their vision statement. 3. [Start your Roadmap](https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/start-your-project-roadmap/) and comment on your issue with your draft Roadmap. 4. Review notes from last cohort call to see if there was something else that was mentioned as homework or assignment ## Week 5 - Agenda: https://openlifesci.org/ols-4/schedule/#week-05 **Roll call** - - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-04 **Links to your assignments to share with your mentor** open canvas:https://docs.google.com/presentation/d/14_gWOer8GHOllcfdUcLl4rBr_yYDsr37fKYTBn1m8l0/edit?usp=sharing ### Agenda and Notes - Check-in ritual. (2-3 minutes) - dario had an almost sunny week - Nadine's was a bit cloudy (applies to both weather & work) - Gratitude ritual. (2-3 minutes) - Nadine: Happy that the side effects of the covid vaccine lasted only 1 day - I'm hapy to work with my lab mates that made possible to publish our last work - Review your goals and progress you’ve made towards them. Any challenges to mention? (5 minutes) - - Review your progress in last weeks and what you would like to present in your final calls. (10 minutes) - make a separate public github repo - use the points discussed to make supervisors understand open science value for your/their career - discuss experts next time - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - (your notes) - Any expert to invite to the future mentor meetings (2-3 minutes). - - Anything else: - (your notes) ### After this call **Next week: Cohort call** - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-06 **Assignments before the next cohort call** - https://openlifesci.org/ols-4/schedule/#week-04 ## Week 7 - Agenda: https://openlifesci.org/ols-4/schedule/#week-07 **Roll call** - dario had a week of showers - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-06 **Links to your assignments to share with your mentor** ADD LINKS TO YOUR ASSIGNMENTS MENTIONED IN THE LAST COHORT CALL ### Agenda and Notes - Check-in ritual. (2-3 minutes) - (your notes) - Gratitude ritual. (2-3 minutes) - (your notes) - Review your goals and progress you’ve made towards them. Any challenges to mention? (5 minutes) - Using Matlab functions via oct2py() takes much much longer. :( - Review your progress in last weeks and what you would liek to present in the your final calls. (10 minutes) - I probably want to present my library (showing it on screen), no matter its stage, maybe also with some plotting function implemented. - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - Thinking about a title for the library - any fancy ideas? - Any expert to invite to the future mentor meetings (2-3 minutes). - Suggestions: Jessica Scheick (has also written Python libraries!), Yo Yehudi (software development), Anne Fouilloux (FAIR software engineering), Himanshu Garg (works on open source software), Guisepe Profiti (software development) - Need to prepare an invitation: https://hackmd.io/@openlifesci/expert-guide - Questions/topics to discuss: - How to make sure system requirements are met? Using a docker image (or something else)? What do I generally need to bear in mind, if I want others to use my library on their computers? (Let’s suppose, it’s functioning on my computer.) - Unit testing: What can I test for apart from the easy stuff (like checking size & type of variables)? What about higher-level integrated unit testing? - Getting into the nitty-gritty - code review - Also, any general remarks about the organization of the code? Anything I am fundamentally missing? - Anything else: - Possibility to do code review by Dario? ### After this call **Next week: Cohort call** - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-08 **Assignments before the next cohort call** - CHECK HERE: https://openlifesci.org/ols-4/schedule/#week-06 ## Week 9 - Agenda: https://openlifesci.org/ols-4/schedule/#week-09 **Roll call** - - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-08 **Links to your assignments to share with your mentor** ADD LINKS TO YOUR ASSIGNMENTS MENTIONED IN THE LAST COHORT CALL ### Agenda and Notes - Check-in ritual. (2-3 minutes) - (your notes) - Gratitude ritual. (2-3 minutes) - (your notes) - Review your goals and progress you’ve made towards them. Any challenges to mention? (5 minutes) - Success: Unpublished bits of the code that I use will be published soon! (Asked the respective authors who will now push the changes ultimately.) - Review your progress in last weeks and what you would like to present in the your final calls. (10 minutes) - (your notes) - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - Dario (& potentially Alessandro) will review the code: - general review - porting Matlab functions to C/C++ (by Alessandro)? Nadine will ask about permissions! - Any expert to invite to the future mentor meetings (2-3 minutes). - Nadine will invite the experts suggested in previous meetings. - Anything else: - Some info for the code review: in [emergence_complexity_measures_analysis.py](https://github.com/nadinespy/EmergenceComplexityMeasuresComparison_Python/blob/master/scripts/emergence_complexity_measures_analysis.py), the main function (with both positional and optional arguments) of my library is executed: emergence_result = ecmc.compute_emergence(emergence_measures[n], sim_data, time_lag = time_lag, redundancy_func = redundancy_func). The library itself with all necessary definitions is called [emergence_complexity_measures.py](https://github.com/nadinespy/EmergenceComplexityMeasuresComparison_Python/blob/master/emergence_complexity_measures_comparison/emergence_complexity_measures_comparison.py). - The general design of the github repository is adapted from https://github.com/uwescience/shablona. ### After this call **Next week: Cohort call** - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-10 **Assignments before the next cohort call** - CHECK HERE: https://openlifesci.org/ols-4/schedule/#week-08 ## Week 11 - Agenda: https://openlifesci.org/ols-4/schedule/#week-11 **Roll call** - - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-10 **Links to your assignments to share with your mentor** ADD LINKS TO YOUR ASSIGNMENTS MENTIONED IN THE LAST COHORT CALL ### Agenda and Notes - Check-in ritual. (2-3 minutes) - (your notes) - Gratitude ritual. (2-3 minutes) - (your notes) - Review your goals and progress you’ve made towards them. Any challenges to mention? (5 minutes) - (your notes) - Review your progress in last weeks and what you would liek to present in the your final calls. (10 minutes) - (your notes) - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - (your notes) - Any expert to invite to the future mentor meetings (2-3 minutes). - (your notes) - Anything else: - (your notes) ### After this call **Next week: Cohort call** - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-12 **Assignments before the next cohort call** - CHECK HERE: https://openlifesci.org/ols-4/schedule/#week-10 ## Week 13 - Agenda: https://openlifesci.org/ols-4/schedule/#week-13 **Roll call** - - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-12 **Links to your assignments to share with your mentor** ADD LINKS TO YOUR ASSIGNMENTS MENTIONED IN THE LAST COHORT CALL ### Agenda and Notes - Check-in ritual. (2-3 minutes) - (your notes) - Gratitude ritual. (2-3 minutes) - (your notes) - Review your goals and progress you’ve made towards them. Any challenges to mention? (5 minutes) - (your notes) - Review your progress in last weeks and what you would liek to present in the your final calls. (10 minutes) - (your notes) - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - (your notes) - Any expert to invite to the future mentor meetings (2-3 minutes). - (your notes) - Anything else: - (your notes) ### After this call **Next week: Cohort call** - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-14 **Assignments before the next cohort call** - CHECK HERE: https://openlifesci.org/ols-4/schedule/#week-12 ## Week 15: Final ols-4 mentor-mentee call - Agenda: https://openlifesci.org/ols-4/schedule/#week-15 **Roll call** - - ### Before this call - review notes from the cohort call linked here: https://openlifesci.org/ols-4/schedule/#week-14 **Links to your assignments to share with your mentor** ADD LINKS TO YOUR ASSIGNMENTS MENTIONED IN THE LAST COHORT CALL ### Agenda and Notes - Check-in ritual. (2-3 minutes) - (your notes) - Gratitude ritual. (2-3 minutes) - (your notes) - Review your goals and progress you’ve made towards them. Any challenges to mention? (5 minutes) - (your notes) - Review your progress in last weeks and what you would liek to present in the your final calls. (10 minutes) - (your notes) - Review your GitHub repo and get any help you need adding your content developed through the assignment from last week (5-10 minutes) - (your notes) - Final wrap up, reflections and gratitude exchange! - (your notes) ### After this call **Next week: Cohort call** Final Graduation! - Shedule, time and agenda: https://openlifesci.org/ols-4/schedule/#week-16 **Assignments before the next cohort call** - None

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully