Tim Coalson

Results 103 comments of Tim Coalson

> Notwithstanding the issue of oblique slice planes, I think there is also the unknown of whether in its "2D" correction mode Siemens is first computing the full 3D correction...

Huh, weird that the scanner even allows 2D correction on a 3D sequence. The correct (3D) solution is the same regardless of 2D or 3D acquisition, so it seems moot...

I'd also note that your captures may be autoscaling based on the data values, and in particular the third one may actually have much smaller differences than the other two.

> > I have set all colorscale limits from -10 to 10 for comparison, so gray is 0) Ah, sorry. I'm not sure how what should be interpolation error (3)...

> Why did we add a second copy of the 164k meshes to this? We already had these meshes in the pipelines. Because the existing names were inconsistent and confusing...

`--grayordinates-res` is more readable and is obviously related to `--grayordinatesres`. I don't know that we expect anyone to copy and paste option flags between any other pipeline and TransmitBias (the...

I added support in case someone copy-pastes `--gdcoeffs` or `--grayordinatesres` from another pipeline. I'd prefer to keep the more readable names in the help info.

I have no specific objections. @effigies would it be good to merge #17 first?

@effigies you said this, which suggests something might get angry if pypi is still holding the name: https://github.com/Washington-University/gradunwarp/pull/17#issuecomment-1901277743 What would the effects be?