-
Olivier Sauter authoredadded more cases and tested with GUIprofs, proffit, toray_automatic so ready to move to new gdat, tag this version first to gdat_v3_9 git-svn-id: https://spcsvn.epfl.ch/repos/TCV/gdat/trunk@5020 d63d8f72-b253-0410-a779-e742ad2e26cf
Olivier Sauter authoredadded more cases and tested with GUIprofs, proffit, toray_automatic so ready to move to new gdat, tag this version first to gdat_v3_9 git-svn-id: https://spcsvn.epfl.ch/repos/TCV/gdat/trunk@5020 d63d8f72-b253-0410-a779-e742ad2e26cf
README 1.02 KiB
gdat.m was first created to get JET data using jetRDA system
It is now generalised to be machine independent in its structure and trace name.
Each machine dependent functions should be in respective directory
Adding a new machine means:
create new subdirectory
change gdatpaths
In new subdirectory, named say: NEWMACHINE
create function: loadNEWMACHINEdata.m (for load NEWMACHINE data)
etc.
The explanation of the different traces are in "help gdat" for generic names.
The specificity of a given machine are in "help loadNEWMACHINEdata"
Thus the head comments of these functions should be correctly updated and self-explanatory
2015/09/17 tag the version before copying new gdat in crpptbx_new to the crpptbx case and removing loadTCVdata
note that AUG will not work for a while, but will be repaired next week....
svn cp https://crppsvn.epfl.ch/repos/TCV/gdat/trunk https://crppsvn.epfl.ch/repos/TCV/gdat/tags/gdat_v3_9 -m"last version before changing to new gdat with machine_mapping file, first TCV is modified"