You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just want to start a conversation about how this will go. Split out bathy_smoother and the toolbox(es) as their own repos? Leave the examples here? If the pycnal code becomes its own thing, is pycnal/PyCNAL going to be a problem?
@braney, would you like to do the conversion since you have a branch? I wouldn't want to mess you up.
The text was updated successfully, but these errors were encountered:
I don't have a very good sense for how all the pieces of the existing PyCNAL organization work together. For example, why is bathy_smoother separate from pycnal_toolbox (formerly pyroms_toolbox)?
I suggest we use the wiki to work out how we want things organized. I made a page:
As for my branch, I actually created a separate directory ("mom6_tools") under PyCNAL, since I didn't want to make major changes to the existing pieces. I'm OK with performing the reorganization or not, but I think we should plan it out first and make sure everyone is on board.
I just want to start a conversation about how this will go. Split out bathy_smoother and the toolbox(es) as their own repos? Leave the examples here? If the pycnal code becomes its own thing, is pycnal/PyCNAL going to be a problem?
@braney, would you like to do the conversion since you have a branch? I wouldn't want to mess you up.
The text was updated successfully, but these errors were encountered: