Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
I will keep track of each discrete set of inputs in a folder. While using Git is a potentially possible, tracking large, possibly binary files still doesn't seem feasible in Git. So, for example, I will set up this directory structure as such:
I will keep track of each discrete set of inputs in a folder. While using Git is a potentially possible, tracking large files still doesn't seem feasible in Git. So, for example, I will set up this directory structure as such:
I will keep track of each discrete set of inputs in a folder. While using Git is potentially possible, tracking large, possibly binary files still doesn't seem feasible in Git. So, for example, I will set up this directory structure as such:
Edit: Perhaps the following question is clearer: what is the best way for me to communicate the fact that the subordinate script should write its output to a certain directory? Should the script even know it where it should write its output, or would it be better to try to write it to something like stdout? The approach I describe above requires the user to know that their script needs the explicit interface defined above, and I don't know if that is good design.
Edit: Perhaps the following question is clearer: what is the best way for me to communicate the fact that the subordinate script should write its output to a certain directory? Should the script even know it where it should write its output, or would it be better to try to write it to something like stdout? The approach I describe above requires the user to know that their script needs the explicit interface defined above, and I don't know if that is good design.
