The interface every system that needs transformation between two quantum mechanical pictures must present towards the trajectory drivers. More...

#include <Exact.h>

Inheritance diagram for structure::Exact< RANK >:

Collaboration diagram for structure::Exact< RANK >:

Public Types
typedef boost::shared_ptr< const Exact >	Ptr

typedef quantumdata::Types< RANK >::StateVectorLow	StateVectorLow

Public Types inherited from structure::ExactCommon
typedef boost::shared_ptr< const ExactCommon >	Ptr

Public Member Functions
void	actWithU (double t, StateVectorLow &psi, double t0) const
	Describes the operation which transforms from interaction picture to the normal picture: $\ket{\Psi(t)}\rightarrow U(t,t_0)\ket{\Psi}$ . More...

Public Member Functions inherited from structure::ExactCommon
bool	applicableInMaster () const
	Describes whether the system fulfills the requirement to be used in Master-equation evolution. More...

Detailed Description

template<int RANK>
class structure::Exact< RANK >

The interface every system that needs transformation between two quantum mechanical pictures must present towards the trajectory drivers.

Experience shows that even when a system uses interaction picture (which is automatically the case if any of its subsystems does) – that is, part of its dynamics is solved exactly – it may still want to calculate the jump operators and quantum averages in the normal picture. (cf. Cases 1 & 3 above.) This is useful e.g. to reuse the code written for the non-interaction-picture case.

In this case, the framework has to be provided with some means to transform between the two pictures. This is fulfilled by this class, from which classes describing such systems have to inherit.

E.g. if quantumtrajectory::MCWF_Trajectory sees that the simulated system inherits from Exact, then it will make the coherent part of the evolution in interaction picture, whereupon it transforms back to normal picture, so that all the rest (jump rates, eventual jumps, quantum averages) can be calculated in this latter picture. This makes that the two pictures coincide before each timestep. (Cf. also the stages described @ quantumtrajectory::MCWF_trajectory.)

Template Parameters

RANK	arity of the Hilbert space
IS_TWO_TIME	default `true`, the most general case

See also: The design is very similar to that of Hamiltonian & HamiltonianTimeDependenceDispatched.

Definition at line 57 of file Exact.h.

Member Function Documentation

template<int RANK>

void structure::Exact< RANK >::actWithU	(	double	t,
		StateVectorLow &	psi,
		double	t0
	)		const

inline

Describes the operation which transforms from interaction picture to the normal picture: $\ket{\Psi(t)}\rightarrow U(t,t_0)\ket{\Psi}$ .

Parameters

[in]	t
[in,out]	psi	$\ket{\Psi}$
[in]	t0

Definition at line 67 of file Exact.h.

The documentation for this class was generated from the following file:

structure/Exact.h

Public Types

Public Member Functions

Detailed Description

template<int RANK> class structure::Exact< RANK >

Member Function Documentation

template<int RANK>
class structure::Exact< RANK >