How to build an interface to my data?

AI Thread Summary
Creating an interface for data overview is a key goal for numerical relativists managing simulations. The current organization method involves using date-labeled directories for input and output files, but challenges arise with input file management due to their branching nature, making SVN unsuitable. A desire exists for an interface that provides insights into simulation runs and input file lineage. The discussion suggests exploring existing projects that may address similar issues, indicating a need for resources or tools tailored to the unique requirements of numerical physics data management. Additionally, programming in Perl is recommended for handling ASCII data, highlighting its utility in data extraction and reporting.
atoasttoall
Messages
3
Reaction score
0
I've long been planning to create an interface which provides an overview of my data. I'm not sure how to get started so I'm looking for advice.

I'm a numerical relativist and I do a lot of simulations. I organize these by running in directories which I label by date. These directories contain the input files that setup the run and the output that results.

The code that we use is in an svn repository and that seems to work pretty well. It's the input files that are the problem. I don't think svn is the right approach for dealing with them. They tend to branch a lot, but rarely merge.

I'd love to have an interface that gave me an overview of the runs I've done and the lineage of the input files for each run. It's hard to imagine that I'm the first numerical physicist to have this problem so there must be projects out there that deal with this, but I don't know where to look. Any suggestions?

Thanks,
atoasttoall
 
Technology news on Phys.org
If you are a numerical relativist, you would certainly know how to programme.
You can take a look at the language Perl, or
PERL - Practical Extraction and Report Language
if your data are in ASCII format, Perl can do a lot for you.
 
Thread 'Is this public key encryption?'
I've tried to intuit public key encryption but never quite managed. But this seems to wrap it up in a bow. This seems to be a very elegant way of transmitting a message publicly that only the sender and receiver can decipher. Is this how PKE works? No, it cant be. In the above case, the requester knows the target's "secret" key - because they have his ID, and therefore knows his birthdate.
Back
Top