changes

Packages/MIES/DC_proc.ipf

@@ -283,6 +283,8 @@ function plot_i_dc(AD)
 
 	wave peakx, peaky
 	display/l=l_i i_wave
+	AutoPositionWindow
+
 	appendtograph/l=l_dc dc_wave
 	SetAxis/A=2 l_i
 	SetAxis/A=2 l_dc
@@ -695,6 +697,8 @@ function plot_psc_a_wave(AD)
 	string wave_name = "PSC_analysis_AD_"+num2str(AD)
 	wave psc_a_wave=$wave_name
 	display/l=lb psc_a_wave[][1] vs psc_a_wave[][0]
+	AutoPositionWindow
+
 	appendtograph/l=ls psc_a_wave[][2] vs psc_a_wave[][0]
 	appendtograph/l=lc psc_a_wave[][3] vs psc_a_wave[][0]
 	Label lb "holding (pA)";DelayUpdate
@@ -704,6 +708,9 @@ function plot_psc_a_wave(AD)
 	SetAxis lb *,0
 	SetAxis ls 0,*
 	SetAxis lc 0,*
+
+	// lines and markers
+	ModifyGraph mode=4
 end
 
 /// Creates a wave with a slice of trace around the i'th peak, see column 0 in the events wave
@@ -792,7 +799,8 @@ function plot_events_sweeps(start, stop, AD)
 	variable start, stop, AD
 	variable i
 
-	display
+	Display
+	AutoPositionWindow
 
 	for (i=start; i<=stop; i+=1)
 		string sweep_df_name="X_"+num2str(i)
@@ -918,6 +926,8 @@ Function RunAll()
 	variable sweepNo = 50
 	variable AD = 10
 
+	make_psc_analysis_wave(AD)
+
 	KillWindows(winList("Graph*", ";", "WIN:1"))
 
 	DFREF deviceDFR = GetDeviceDataPath("ITC1600_Dev_0")
@@ -932,12 +942,7 @@ Function RunAll()
 
 	SetDataFolder dfr
 	plot_i_dc(10)
-End
 
-// Questions for chat:
-// - Is everything important plotted? I.e. Do you need more info to decide on accepted/rejected?
-// - Is there a default (accepted/rejected/undecided) for each event?
-// - How should we implement the UX for peak acceptance/rejection?
-//   One could make clicking the marker toggle the state. I would also use a non-filled circle.
-// - tau_d/tau_r are currently not calculated. Should they?
-// - Does it make sense to plot the events on the deconvoluted data?
+	Edit/K=1 root:psc_folder:PSC_analysis_AD_10.ld
+	Edit/K=1 root:MIES:HardwareDevices:ITC1600:Device0:Data:X_50:AD_10_events.ld
+End