Next steps and directions: Speeding up bottlenecks, adding features and all that

occam-ra / occam

OCCAM Reconstructability Analysis Tools

Other

20 stars 14 forks source link

Next steps and directions: Speeding up bottlenecks, adding features and all that #18

Open venkatachalapathy opened 5 years ago

venkatachalapathy commented 5 years ago

I don't know if you all have other things in mind but these are some of the things one could do once occam-ra is readied for general use. These are some of the things I have on my wish list. There are questions regarding implementing more efficient state-space searches that Marty talks about but I suspect those are things that are probably on the pipeline.

identifying computational bottlenecks and speeding up things like IPF and margin calculations (all clearly defined doable tasks) (Are there others like this?)
straightforward extensions like including latent variables and hidden Markov models
and more elaborate extensions like embedding Pearl's causal inference and mediation analysis within occam-ra or creating interfaces so that we can talk to existing R packages that do these jobs

gdcutting commented 5 years ago

Hey, someone read my email! Thanks Rajesh, this is a great start to the discussion. Some specific (short-term) issues are already in the tracker, but this is a great place for discussion about long-term goals, extensions, etc.

It is going to take me a few weeks probably to go through the code and understand it well enough to start making even small changes, so there might not be any apparent code changes in the very short term. But it will happen, it will just take a little time. Having the conversation here helps me wrap my head around it a lot better, the email thread can get unweildy, and if you're trying to see things by topic it's just impossible.

gdcutting commented 5 years ago

I think over the next few weeks we can have a great discussion about how to balance time between maintaining and fixing the existing code, improving it (adding new features) within the same project structure, possibly refactoring or updating some of the python code (which might be more of an issue when the capstone project gets going), and other things. I am also splitting time between understanding the code and working on content for the .io page, so right now I'm very aware of how finite my time is. Hopefully we will have some help soon from the Capstone team and others.