one way is for procedure to issue alert messages about changes in parameters. ![]() analysis 'cos parameters are not unique. then old parameters might still get used for some one exception is when new analysis means new parameters not new procedure. no need to check in history file for date this way just by looking at output wave one can know. ways to identify if newer analysis was used any new analysis will obviously use new analysis 'cos there is only one copy of PraveensIgorUtilities. After a change is made in an analysis procedure how to make sure that new analysis is used in all subsequent analysis? of the dimension of pair of waves to be acted on choose smaller dimension modified pt_OperateOn2Waves() to operate on multiple waves matching the DataWaveMatchStr and also instead of choosing bigger Modified pt_BinXYWave() to exclude Nans and Infs when checking if all points got binned once and only once ![]() In pt_LoadWFrmFldrs added the option to load a specific wave rather than all waves (eg. In pt_SpikeAnal, added ISIMidAbsX (ISI mid-point) and ISVY (Interspike voltage calculated at ISIMid point) 8 In pt_CalBLAvg if no points to average (start or end point =Nan), do not create any wave. 7 modified pt_AverageVals() so that the parameter wave can be chosen from current data folder before looking in root:FuncParWaves ![]() instead comment out the sleep in earlier window and put a sleep /T 30 is that during sleep the data and results from last calculation are displayed. problem is that this way the current data and current results are not displayed properly. now append new raw and calculated data. 6 in case where the calculated result is displayed on top of raw data, the following logic was being used. In pt_CurveFit() set the default values of output fit parameters to NaN. for 0th point there is no point before // (found while analyzing spontaneous activity data which were the 1st 10 waves) 11_17_2008 praveen. 4 In pt_SpikeReAnal small bug for extracting ExtractParW corresponding to 0th index value of NSpikesInTrainW. SAME NEEDS TO BE DONE FOR pt_RsRinCmVmIclamp2, pt_RsRinCmVmVclamp2 IN THIS FILE AND OTHER FROZEN VERSIONS OF THIS FILE Earlier weird value of tempRs was getting used in further calculations 11_02_2008. 3 In pt_RsRinCmVmIclamp2 if weird value of TempRs then it should not be used in further calculations (like RIn). seems that inverse ratio is more commonly used. ![]() inverted the definition of adaptation ratio in pt_CalISIAdaptRatio(). pt_AverageVals can then be used to get RsV values during the recordings. Also Renames RsV that is generated to RsVXXXpA changes the current injection values and wavenames before calling pt_CalRsRinCmVmIClamp. (initial transient is small for the seal test current), i am using the current injected for evoking spikes to measure the transient. As in current clamp Rs measurement is difficult Coded pt_CalRsRinCmVmIClampVarPar1() which is a wrapper for pt_CalRsRinCmVmIClamp. GENERAL IF ANALYSIS IS REDONE JUST BEFORE FINAptLIZING IT, IT SHOULD TAKE CARE OF BOTH CHANGES IN FUNCTIONS AND CHECKING THAT IS TO ACTUALLY LOOK AT THE PARAMETER VALUES USED AND MAKE SURE THEY ARE WHAT THEY SHOULD BE. ANALYSIS CAN ALSO CHANGE IF FUNCTION REMAINS THE SAME BUT PARAMETER VALUES ARE DIFFERENT. CHECKED IF ANY OF THE USED FUNCTIONS HAS BEEN ALTERED AND IF PART OR WHOLE OF THAT DATA NEEDS TO BE ANALYSED. THIS WAY FOR ANY ANALYZED DATA ONE CAN EASILY ANY CHANGES MADE TO THIS FILE SHOULD BE ENTERED (EXPLAINED) HERE. #pragma rtGlobals =1 // Use modern global access method.
0 Comments
Leave a Reply. |