Skip to content
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

Should we remove legacy code that no understands? #6

Open
jjmaldonis opened this issue Apr 5, 2016 · 2 comments
Open

Should we remove legacy code that no understands? #6

jjmaldonis opened this issue Apr 5, 2016 · 2 comments

Comments

@jjmaldonis
Copy link
Contributor

Right now I think there are some code blocks that no one understands. They are all in version control now, so should we just delete them? This would help us keep track of the working code more easily imo.

@jjmaldonis
Copy link
Contributor Author

For example, there are a whole bunch of fuss files in selection. Do we need/want them all?

There are also files with the names: fitpred.py, fitpred_bests.py, fitpred_new.py in the predator directory. Do we want all three of those? Or is fitpred_new.py the "new" one that we want?

Same with io/read_xyz_v0.py and io/read_xyz.py. Can we avoid this since they are all in version control anyways?

@ZhewenSong
Copy link
Contributor

I agree removing older versions of code like io/read_xyz_v0.py. But something like fuss is just a selection scheme and I don't think we should remove them at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants