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 extract crowdastro.crowd into its own project? #212

Open
chengsoonong opened this issue Oct 19, 2016 · 2 comments
Open

Should we extract crowdastro.crowd into its own project? #212

chengsoonong opened this issue Oct 19, 2016 · 2 comments
Labels

Comments

@chengsoonong
Copy link
Owner

https://github.com/chengsoonong/crowdastro/tree/master/crowdastro/crowd

This would mean that we may need to tinker a bit with the interface, but it might be a tool that is of broader interest than just applying it to RGZ.

@MatthewJA
Copy link
Collaborator

Yes, I think we should. Generic crowd algorithms are notably different from astronomical applications. (Then again, it is _crowd_astro...)

If we do that, we should do it after the thesis, and we should also discuss the API.

@chengsoonong
Copy link
Owner Author

I will explicitly tag issues with thesis if I think you should include it.

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

No branches or pull requests

2 participants