-
Notifications
You must be signed in to change notification settings - Fork 18
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
deprecate things that are not being done properly #44
Comments
Considering the If this is not wanted in the |
I don't even know what's in |
I mean that's up to you and maybe a separate repo is easier to maintain. I personally think that providing some analysis tools for workflow in the same repo would be more convenient, though. So far some of us have been using functions like |
@gabor1 where should we put these things? |
Just to collect some other things to revise:
|
@bernstei what's wrong with |
It's sort of OK, since it does use |
Very small nitpick, but might I suggest that all style elements be removed from the plotting section? Seems like that is something that the users can easily set via their plt.rcParams. So instead of defining a sequence of colors, we just define:
and iterate through those parameters. The figsizes, labelsizes, etc. would then all be taken directly from the user's individual setups. An alternative approach would be to provide a default rcParams file somewhere, which would then be the fallback. |
providing a default rcParams would be good. not everyone controls their styles by rcParams files |
Comments on what's there now:
I think that As for |
Current plan:
@gabor1 sounds OK to you? Do we have a better name for the user directory for Tamas's code? |
I am OK with deprecating them, if we even want to re-use them then git remembers everything. Feel free to go ahead with purging this part of the codebase.
… On 5 May 2022, at 19:21, bernstei ***@***.***> wrote:
Current plan:
reactions_processing, neb, ts, radicals to user/reactions (name to be finalized)
plotting to deprecate/plotting, to be moved into a separate directory or repo for analysis
vib unchanged for now, pending thought about merging with phononpy based code for periodic systems.
@gabor1 <https://github.com/gabor1> sounds OK to you? Do we have a better name for the user directory for Tamas's code?
—
Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJKZU7CGWPSOUV5EIJU3JMDVIQGUBANCNFSM5RLRZ5EA>.
You are receiving this because you were mentioned.
|
Deprecate bits of code that don't do things the workflow way, or just don't use it. They can be updated to do it the right way (so they can be wrapped by
iterable_loop
(soon to beautoparallelize
), or moved to some user-specific place.reactions_processing/
plotting/
some things in
generate
, e.g.neb
,ts
,vib
,radicals
some things in
cli.py
The text was updated successfully, but these errors were encountered: