| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Just some minor points, plus re-pinging @timhoffm in case he has an opinion re: n_input / input_dims naming?
Sorry, something went wrong.
|
Thank you for the feedback @anntzer ! |
Sorry, something went wrong.
|
See #29876 (comment) |
Sorry, something went wrong.
|
Thank you @timhoffm |
Sorry, something went wrong.
|
@QuLogic Thank you again and apologies for my tardiness (I was sick) |
Sorry, something went wrong.
|
This is on hold until we sort out #30149 (Norm Protocol) |
Sorry, something went wrong.
@timhoffm @anntzer I had made these changes, but actually committing them had slipped my mind. They are in now 😅 I'm on vacation now, so my schedule is a bit scrambled. @QuLogic I'll take a look at the rest of your comments soon :) |
Sorry, something went wrong.
Sorry I dropped the ball on this. I can try to have a look but not before the middle of the month or so. |
Sorry, something went wrong.
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
|
@QuLogic all the comments should have been addressed now, do you have the time to take another pass at it? |
Sorry, something went wrong.
There are still a couple of comments that are unresolved/have no reply, at least. |
Sorry, something went wrong.
|
@QuLogic @story645 thank you for your comments and patience on this, I believe i have addressed all the comments now, but please correct me again if there are some I have overlooked. Otherwise I look forward to your future comments :) |
Sorry, something went wrong.
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
Thank you @QuLogic ! |
Sorry, something went wrong.
Yes, I believe a squash merge would be most suitable |
Sorry, something went wrong.
|
Thanks for working your way through this long process. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR summary
This PR continues the work of #28658 and #28454, aiming to close #14168. (Feature request: Bivariate colormapping)
This is part one of the former PR, #29221. Please see #29221 for the previous discussion
Features included in this PR:
Features not included in this PR: