Workflow figure 1 #5
Assignees
Milestone
Comments
|
Hey @garikoitz, any updates on this for tomorrow's meeting? |
|
I'll have it for tomorrow.
Any updates in the WF? Should I still look at the photograph we took of the
board in Seattle? I can add the main steps and review it tomorrow to add
details?
When is it? Tomorrow 12:30 Pacific Time?
…On Mon, Mar 23, 2020 at 11:59 AM Oscar Esteban ***@***.***> wrote:
Hey @garikoitz <https://github.com/garikoitz>, any updates on this for
tomorrow's meeting?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCZAVZ4NZDMEA36INFFWOTRI6WRXANCNFSM4IUFXBTQ>
.
|
I guess so.
Sounds like a plan.
Yes, just sent an invite |
|
Sorry: I messed up my schedule and can't make tomorrow's meeting.
Derek and I will be programming together on zoom 10 AM - noon, but I have
to go at noon.
…On Mon, Mar 23, 2020 at 4:21 PM Oscar Esteban ***@***.***> wrote:
Should I still look at the photograph we took of the board in Seattle?
I guess so.
I can add the main steps and review it tomorrow to add details?
Sounds like a plan.
When is it? Tomorrow 12:30 Pacific Time?
Yes, just sent an invite
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA46NUHFRVZYQEB5JX4JVDRI7VG5ANCNFSM4IUFXBTQ>
.
|
|
I think we can still use the link, right? Let's do a quick catch-up and
I'll write @arokem with the news.
…On Mon, Mar 23, 2020, 18:31 Ariel Rokem ***@***.***> wrote:
Sorry: I messed up my schedule and can't make tomorrow's meeting.
Derek and I will be programming together on zoom 10 AM - noon, but I have
to go at noon.
On Mon, Mar 23, 2020 at 4:21 PM Oscar Esteban ***@***.***>
wrote:
> Should I still look at the photograph we took of the board in Seattle?
>
> I guess so.
>
> I can add the main steps and review it tomorrow to add details?
>
> Sounds like a plan.
>
> When is it? Tomorrow 12:30 Pacific Time?
>
> Yes, just sent an invite
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#5 (comment)>,
or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAA46NUHFRVZYQEB5JX4JVDRI7VG5ANCNFSM4IUFXBTQ
>
> .
>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAESDRUXTQ2FHURJZ6JXX33RJAEQTANCNFSM4IUFXBTQ>
.
|
|
Yes. I believe that the link will still work for you.
On Mon, Mar 23, 2020 at 7:23 PM Oscar Esteban <[email protected]>
wrote:
… I think we can still use the link, right? Let's do a quick catch-up and
I'll write @arokem with the news.
On Mon, Mar 23, 2020, 18:31 Ariel Rokem ***@***.***> wrote:
> Sorry: I messed up my schedule and can't make tomorrow's meeting.
>
> Derek and I will be programming together on zoom 10 AM - noon, but I have
> to go at noon.
>
> On Mon, Mar 23, 2020 at 4:21 PM Oscar Esteban ***@***.***>
> wrote:
>
> > Should I still look at the photograph we took of the board in Seattle?
> >
> > I guess so.
> >
> > I can add the main steps and review it tomorrow to add details?
> >
> > Sounds like a plan.
> >
> > When is it? Tomorrow 12:30 Pacific Time?
> >
> > Yes, just sent an invite
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#5 (comment)>,
> or
> > unsubscribe
> > <
>
https://github.com/notifications/unsubscribe-auth/AAA46NUHFRVZYQEB5JX4JVDRI7VG5ANCNFSM4IUFXBTQ
> >
> > .
> >
>
> —
> You are receiving this because you were assigned.
> Reply to this email directly, view it on GitHub
> <#5 (comment)>,
or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAESDRUXTQ2FHURJZ6JXX33RJAEQTANCNFSM4IUFXBTQ
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA46NRXYLTUW2JZAJDM6QDRJAKTBANCNFSM4IUFXBTQ>
.
|
oesteban
added a commit
that referenced
this issue
Oct 27, 2020
I have taken a stab at mapping the whiteboard scribbles of our sprint into an SVG file. I've realized of several things I will go over in our weekly meeting (in 30 min aprox): - *dMRIPrep* SHOULD NOT concatenate runs (#43) - SDC (fieldmaps) requires transferring almost all responsibilities over to *SDCFlows* - that includes some of the issues that @mattcieslak raised within #43. - We need to reconsider where denoising should be inserted (and listen what @jelleveraart has to say about this). The question is would denoising help have a better estimation of head motion and/or Eddy deformations? Hopefully, this will help us progress faster towards our roadmap. Resolves: #5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update fMRIPrep's workflow graph, and upload to repo.
The text was updated successfully, but these errors were encountered: