https://nf-co.re logo
Join Slack
Powered by
# proteinfold_dev
  • j
    Hi <!channel> @mashehu nicely agreed to join our meeting, only that due to logistic issues we will need to to shift our meeting to 9:30 CEST / 5:30 AEST. Since it would be great for as many of us as possible to attend, we’d like to propose two possible dates so you can choose the one that works best: 🥝 25th June - 9:30 CEST / 5:30 AEST 🍎 2nd July - 9:30 CEST / 5:30 AEST
    🍅 2
    🥝 3
  • j
    Once we agreed on the date, I will share a link to the zoom meeting
  • j
    Hi, tomorrow I will suggest to skip the meeting and go directly to the one of the 2nd of July that will be with Matthias to discuss what we agreed on the last one
    🙌 1
  • j
    Hi <!channel> The development meeting from now will be Thursday at 9:00 as voted on the poll 🤝🏻 Exceptionally, next Thursday we will start at 9:30 so that Matthias can join us 📆 Find attached the invitation and here the link to the meeting 👉🏻 https://rediris.zoom.us/j/91439018530
    meeting-91439018530(1).ics
    🙌 2
    🙌🏻 1
  • e
    This is today, right? 😄
    👍 1
    👍🏻 2
  • j
    Launching meeting now
    m
    • 2
    • 2
  • j
    Regarding the ro-crate not updating the path to the metro map figure, I renamed the metromap to 2.1: github.com/nf-core/…/images However, again the ro-crate has the previous version, probably will need to update it manually somehow (will do it) 👉🏻 github.com/nf-core/proteinfold/blob/…/ro-crate-metadata.json#…
    t
    m
    • 3
    • 3
  • j
    Hi, Tomorrow I can only start the meeting at 9:30 because I need to drop off the kids first. Please react with 👍🏼 if this is okay with you, or 👎🏼 if it is not.
    👍 2
    👎 1
    👍🏻 1
    👎🏻 1
    e
    • 2
    • 3
  • j
    Hi <!channel> Just a reminder of tomorrow development meeting at 9:00 CEST/5:00 AEST, usual link, see you tomorrowc
    👍 1
  • j
    <!channel> meeting starting now
    t
    • 2
    • 2
  • j
  • e
    latest template should have changed linting from 
    pre-commit
    to 
    prek
    ..so if you make that update, this piece of code should vanish anyway: github.com/nf-core/proteinfold/…/1 Latest version of fix_linting.yml: github.com/nf-core/proteinfamilies/blob/…/fix_linting.yml Shall I open a PR? Was there something particular to proteinfold in that file? Edit: latest dev -> main PR should fix this! prek is already there
    🙌🏻 1
  • j
    I have merged the PR in test-datasets, I think it would be nice to have a README that describes the different files, but this can be done in a different PR not to stop the other PRs in the proteinfold repo
  • j
    Hi <!channel> tomorrow's development meeting around 9:15 CEST/5:15 AEST, I can do it earlier sorry, usual place
    👍 1
    j
    • 2
    • 1
  • j
    Meeting starting now
  • j
    In case someone fancies reviewing it 👉🏻 github.com/nf-core/proteinfold/pull/645
  • j
    Hi <!channel> tomorrow’s development meeting around 9:15 CEST/5:15 AEST, I can do it earlier again this week, usual place
  • j
    Sorry I will need 5 minutes more
    👍 2
  • j
    I am having issues accessing my instituional account, let's meet here instead: us04web.zoom.us/j/79221123083?pwd=…
  • j
    sorry
  • t
    no stress
  • j
    Hi, just an update about the full test, I launched the test yesterday but only one start to run (and it is stacked) and all the others appear as submitted but did not start running… 😓
    😢 1
  • t
    pipeline problem or infra problem?
  • j
    They are just submitted and not running so I guess that it is a problem in the config of the test in the yaml file or a infrastructure error but didn't have time to look into it
  • j
    Just asked in #CTY8L26C8 for feedback
    👍 1
  • e
    Github runners had problems picking tests yesterday for me as well..so might be connected
    👍🏻 1
  • j
  • j
    FYI ☝🏻
  • j
    Hi! Can someone review the template merge 👉🏻 github.com/nf-core/proteinfold/pull/655
    👀 1
    k
    • 2
    • 3
  • j
    Hi <!channel> Someone is creating the colabfold module in nf-core: github.com/nf-core/modules/pull/13066 It might be good to take a look on it and check whether anything will stop us from using it in the pipeline with the proposed implementation
    this 1
    👀 1