-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roadmap for future development of DomainSets #150
Comments
Pinging a few people, consider this for-your-information: @dlfivefifty @oschulz @aplavin @hyrodium @zsunberg @cscherrer |
Update: the first item (factoring out maps) is largely done. All map code now lives in a submodule FunctionMaps.jl, which has its own test suite and could turn into a separate package. For now, everything is backwards compatible (or so it should be) and the internal change happened in v0.7.10. |
Thanks for keeping us up to date, @daanhb ! |
Here are a few areas I'm thinking of to improve DomainSets. I'm linking to existing issues.
jacobian
#87)approx_in
), usingatol
andrtol
arguments. It's important to get this right, since we've been so careful about distinguishing between open and closed domains as well. (use atol and rtol in approx_in #124)I've been playing with a DomainSetsCore package, but I don't think it is essential to move forward so it's not on the list.
Ideally, these improvements make DomainSets smaller and yet more functional.
The text was updated successfully, but these errors were encountered: