Thanks. I have been meaning to look at that.
On Thu, 7 Jan 2021 at 23:33, Joe Bogner <[email protected]> wrote: > > Jupyter notebooks may help you with organizing your research - > https://code.jsoftware.com/wiki/Guides/Jupyter > > This has been my preferred tool - far above Excel. > > On Thu, Jan 7, 2021 at 2:39 PM Justin Paston-Cooper <[email protected]> > wrote: > > > I am open to suggestions. Right now I'm researching a lot of related > > things concurrently. I'm storing some of the results in TSV files. > > Some of the scripts are Python, some are curl | jq | awk. Some of the > > results I am storing as variables in J scripts. I am constantly going > > back and forth between differing representations, differing > > environments, recalculating things needlessly, and so on. > > > > I am looking for a way to better organise my research. If not > > spreadsheets, do you have some advice on how to coordinate all this > > separate data in one place? A Make file could be a start, but this > > doesn't satisfy the requirement of having a nice editable GUI to > > arrange and display all the separate sources of data. Maybe wd would > > be a start in that direction. I haven't researched the alternatives. > > > > How do you organise your research? > > > > Application: Researching interactions between prices of a set of > > things in each of a set of places. There are many different analyses > > that can be made. I am finding it hard to keep track of all the angles > > I have looked at. These angles all reside in separate directories, > > which is not ideal. I have hand-written notes, but those need to be > > updated by hand. > > > > By the way, I wasn't envisioning doing any calculation in the > > spreadsheet. The idea of the spreadsheet was simply to coordinate > > communication and (re)calculation between various calculation > > processes, display the results, and allow the display of the results > > to be edited. > > > > Imagine an actor system with the spreadsheet being the coordinator. > > > > On Thu, 7 Jan 2021 at 20:23, Devon McCormick <[email protected]> wrote: > > > > > > It would be remiss of me not to mention that you really ought to > > > re-consider making a spreadsheet an integral part of your design, not the > > > least due to the historically high rates of error that have been measured > > > in spreadsheets - 1 to 5%: > > > https://arxiv.org/ftp/arxiv/papers/1602/1602.02601.pdf . It seems > > > incongruous to worry about the sixth decimal place in numbers with many > > > digits before the decimal point but ignoring error rates that dwarf this > > > imprecision. > > > > > > By way of comparison, in most code-bases where people measure errors, an > > > error rate of 10 bad lines per 1000 lines of code would be considered > > > unacceptably high. > > > ---------------------------------------------------------------------- > > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
