You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So it is probably better to call it Representation. An example is the following,
#generic Veretx function in KX representationstruct VerKX
para::DiagPara#DiagPara don't need weightType
spin::Vector{Int}#[Up, Up], [Up, Down], ...
channel::Channel# particle-hole, particle-hole exchange, particle-particle, irreducible, and their counterterms
extK::Vector{Vector{Float64}}
extT::Vector{Int}
order::Vector{Int}#[2, 0, 1] means loop-order 2, and one derivative of the second type.end
it should come with some help functions (for example, a function to check if the vertex is instant or not).
The current implementation of DiagramID duplicates with DIagPara.type.
DiagramID should have larger scope than DiagPara.type. To be more specific,
DiagPara.type --> Ver4, Ver3, Green, Interaction, Sigma, ...
DiagramID --> N-body Vertex/Green/connected-Green in momentum-time representation, spacetime-representation, ...
So it is probably better to call it Representation. An example is the following,
it should come with some help functions (for example, a function to check if the vertex is instant or not).
The Diagram struct should be defined as,
Need some help functions (for example, isbare(diag) = (length(diag.subdiagram)==0))
The text was updated successfully, but these errors were encountered: