Jessica Scheick

Excellent @weiji14! We'd be happy to have you join the team and help make some of these things happen. I agree that leveraging existing libraries is the way to go...

I think you raise a bunch of good points, and perhaps it could be helpful to shift the conversation towards what the best way to handle this is in the...

Update: I would like these resources to include an interactive "how to contribute to icepyx" jupyter notebook that helps with development environment management (e.g. `pip install -e.`) and other tips...

Thanks @bidhya for this example (and apologies it's taken me so long to review your PR - I'm having trouble keeping up since the hackweek). I'm hoping you'd be willing...

@bidhya I'm making my way through some of these older PRs to either incorporate them or close them. I recently used some of the code from this example (with attribution,...

> I think it is best to move the codes to the new notebook you have created. After that I can supplement it with additional details as we both see...

Hello @dbaston! Thanks for reporting this. We're actually in the process of improving our spatial input handling (#322) to address #321 and several other issues (e.g. for inputs that cross...

Hello again @dbaston! This issue should be resolved with #322 and #331 (which will be included in the next release of icepyx, likely sometime in early October). Please let us...

Thanks @kelseybisson! I reordered and tried to clarify - to get the docstrings to show up in the docs, we have to (besides having docstrings) add them to some of...

@learn2phoenix Sure - that would be great! Let me know how I can help.