-
Notifications
You must be signed in to change notification settings - Fork 4
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
New Colormaps #3
Comments
Hi Ali @gha3mi |
These 4 Matplotlib colormaps are for example clearly in public domain / CC0 license: I think we must be sure for all included colormap. |
But these Matlab palettes are copyrighted: |
Sorry, I didn't consider this. I will revert the last changes and, if necessary, remove this issue as well. We can start a new discussion. |
Note also that the file So other collections of colormaps should be defined in other module files. We could have a module for each collection plus one module miscellaneous for example. |
I can work on this on Sunday. Should I create a matplotlib_colormaps for that? |
Thanks for contributing! Yes, Just follow the model of |
The second and third ones are under GPL license, not compatible with our MIT license. The first one is under CC-BY 4.0, so I think it is possible to use it. Although we should verify further the compatibility. The fourth is under BSD 3-clause license, which says for example "Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission". I think that for the time being we should just import colormaps under MIT license or in public domain. In those cases, things are clear... We should also select colormaps considering their quality, and/or their complementarity to the colormaps already included. We probably don't need several too similar colormaps, except maybe if they are classical colormaps in a famous software (a user may be happy to find its preferred maps in ForColormap). |
Before submitting my pull request, I made the following changes: You can view the changes at this link: main...gha3mi:forcolormap:main.
! Other subroutines defined in this module:
! Elaborated colormaps are defined in their own subroutines:
private :: cubehelix_colormap
! Auxiliary functions used by the test method:
private :: write_ppm_test, write_ppm_colorbar
|
Thanks, that looks good!
Probably that will be the way to go as we add more modules... |
I have found the bug in the viridis colormap: 96, 202, 96,&
99, 203, 95,&
01, 203, 94,&
03, 204, 92,&
05, 205, 91,&
...
94, 223, 35,&
97, 224, 33,&
00, 224, 32,&
02, 225, 31,&
05, 225, 29,& The first digit "1" or "2" of the red value is absent. |
@gha3mi I have fixed it thanks to the regex |
Thanks, @vmagnin! This happened because of code formatting. |
Added 'colormap_parameters' module. Added 'miscellaneous_colormaps' module. Removed 'test' type-bound procedure. Moved 'test' subroutine to demo and example1. Added 'colorbar' type-bound procedure. Renamed 'get_current' to 'get_name'. Updated write_ppm_colorbar, set, and print subroutines. Added pure/impure statements. Bug fixes: changed 'intent(inout)' to 'intent(in)' in relevant functions. Updated demo and example1.
|
No description provided.
The text was updated successfully, but these errors were encountered: