Difference between revisions of "Tehnical information"
| Line 4: | Line 4: | ||
Old Mslice kept its whole configuration in msp files. All information a user can see in a Mslice window is stored in an ASCII msp file in a form key = value pairs, where each key corresponds to some visible or invisible field in Mslice GUI. To save whatever you entered into GUI or load your previous data you have to save/load some msp file. | Old Mslice kept its whole configuration in msp files. All information a user can see in a Mslice window is stored in an ASCII msp file in a form key = value pairs, where each key corresponds to some visible or invisible field in Mslice GUI. To save whatever you entered into GUI or load your previous data you have to save/load some msp file. | ||
| − | The disadvantage of this approach is that you always have to start you work loading msp file and if you move msp file between two machines, the paths to data files stored in the msp file will probably become wrong. This is why recent Mslice keeps information about its | + | The disadvantage of this approach is that you always have to start you work loading msp file and if you move msp file between two machines, the paths to the data files stored in the msp file will probably become wrong. This is why recent Mslice keeps information about its last used msp file and paths to data files in configuration (see [[config]]). When choosing between different paths stored in msp or in configuration , an arbitration occurs. The code, which selects what path to use is located in ms_load_msp.m procedure. The fragment of the selection code can be found [[Code_to_identify_data_folders|here.]] |
Latest revision as of 11:44, 31 March 2011
File location for spe and phx files
Old Mslice kept its whole configuration in msp files. All information a user can see in a Mslice window is stored in an ASCII msp file in a form key = value pairs, where each key corresponds to some visible or invisible field in Mslice GUI. To save whatever you entered into GUI or load your previous data you have to save/load some msp file.
The disadvantage of this approach is that you always have to start you work loading msp file and if you move msp file between two machines, the paths to the data files stored in the msp file will probably become wrong. This is why recent Mslice keeps information about its last used msp file and paths to data files in configuration (see config). When choosing between different paths stored in msp or in configuration , an arbitration occurs. The code, which selects what path to use is located in ms_load_msp.m procedure. The fragment of the selection code can be found here.
