FluxTraining.jl


			
			
			
			using
			
			
			 
			
	
		
			FluxTraining
			
			

			
			
			using
			
			
			 
			
	
		
			FluxTraining
			
			.
			
	
		
			Events
			
			,
			
			
			 
			
	
		
			FluxTraining
			
			.
			
	
		
			Phases

Tips & tricks

Listing event handlers for a callback

Use Base.methods to check what events a callback handles:


			
			
			
			methods
			
			(
			
			
	
		
			FluxTraining
			
			.
			
			
	
		
			on
			
			,
			
			 
			
			
			(
			
			Any
			
			,
			
			 
			
			Any
			
			,
			
			 
			
	
		
			Recorder
			
			,
			
			 
			
			Any
			
			)
			
			)

# 4 methods for generic function on:

on(::FluxTraining.Events.EpochEnd, phase::FluxTraining.Phases.Phase, recorder::Recorder, learner) in FluxTraining at /home/runner/.julia/packages/FluxTraining/YVIq2/src/callbacks/recorder.jl:43
on(::FluxTraining.Events.StepEnd, phase::FluxTraining.Phases.Phase, recorder::Recorder, learner) in FluxTraining at /home/runner/.julia/packages/FluxTraining/YVIq2/src/callbacks/recorder.jl:36
on(::FluxTraining.Events.EpochBegin, phase::FluxTraining.Phases.Phase, recorder::Recorder, learner) in FluxTraining at /home/runner/.julia/packages/FluxTraining/YVIq2/src/callbacks/recorder.jl:31
on(::FluxTraining.Events.Event, phase, ::FluxTraining.SafeCallback, learner) in FluxTraining at /home/runner/.julia/packages/FluxTraining/YVIq2/src/callbacks/callback.jl:247

Visualize the callback dependency graph

You can use GraphPlot . jl to visualize the dependencies between callbacks:


			
			
			
			
			learner
			
			 
			
			=
			
			 
			
			
	
		
			Learner
			
			(
			
			
    
			
			nothing
			
			,
			
			 
			
			nothing
			
			,
			
			  
			
			# dummy arguments
			
			
    
			
			
			callbacks
			
			=
			
			
			[
			
			
	
		
			ToGPU
			
			(
			
			)
			
			]
			
			,
			
			

			
			)
			
			;


			
			
			
			using
			
			
			 
			
			GraphPlot
			
			

			
			
			gplot
			
			(
			
			
			
			learner
			
			.
			
			
			callbacks
			
			.
			
			
			graph
			
			,
			
			 
			
			
			nodelabel
			
			 
			
			=
			
			 
			
			
			
			learner
			
			.
			
			
			callbacks
			
			.
			
			
			cbs
			
			,
			
			 
			
			
			layout
			
			 
			
			=
			
			 
			
			stressmajorize_layout
			
			)

(the target of an arrow depends on the origin)

As an example for a detected dependency, we can see that MetricsPrinter runs after Metrics . MetricsPrinter prints the values of all metrics, so [ Metrics ] needs to run first.