Skip to content

Commit

Permalink
Remove particle interface, implementation and tests, they moved to QE…
Browse files Browse the repository at this point in the history
…Dbase (#23)

Fixes #22

Co-authored-by: AntonReinhard <[email protected]>
  • Loading branch information
Anton Reinhard and AntonReinhard authored Oct 12, 2023
1 parent 0074aa0 commit ffd831e
Show file tree
Hide file tree
Showing 7 changed files with 1 addition and 396 deletions.
12 changes: 0 additions & 12 deletions src/QEDprocesses.jl
Original file line number Diff line number Diff line change
@@ -1,9 +1,5 @@
module QEDprocesses

export AbstractParticle
export is_fermion, is_boson, is_particle, is_anti_particle
export mass, charge

# Abstract model interface
export AbstractModelDefinition, fundamental_interaction_type

Expand All @@ -17,19 +13,11 @@ export differential_cross_section, total_cross_section
export AbstractComputationSetup, InvalidInputError, compute
export AbstractProcessSetup, scattering_process, physical_model

# particle types
export AbstractParticleType
export FermionLike, Fermion, AntiFermion, MajoranaFermion
export BosonLike, Boson, AntiBoson, MajoranaBoson
export Electron, Positron, Photon

using DocStringExtensions
using QEDbase

include("utils.jl")
include("interfaces/particle_interface.jl")
include("interfaces/model_interface.jl")
include("interfaces/process_interface.jl")
include("interfaces/setup_interface.jl")
include("particle_types.jl")
end
80 changes: 0 additions & 80 deletions src/interfaces/particle_interface.jl

This file was deleted.

2 changes: 1 addition & 1 deletion src/interfaces/setup_interface.jl
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ Interface function, which asserts that the given `input` is valid, and throws an
```Julia
_assert_valid_input(stp::YourCustomSetup,input)
```
which should throw an exception, which is a subtype of [`AbstractInvalidInputError`](@ref). One may also use the concrete implementation [`InvalidInputError`](@ref) if the input is invalid instead of writing a custom exception type.
which should throw an exception, which is a subtype of [`AbstractInvalidInputException`](@ref). One may also use the concrete implementation [`InvalidInputError`](@ref) if the input is invalid instead of writing a custom exception type.
"""
@inline function _assert_valid_input(stp::AbstractComputationSetup, input)
Expand Down
192 changes: 0 additions & 192 deletions src/particle_types.jl

This file was deleted.

30 changes: 0 additions & 30 deletions test/interfaces/particle_interface.jl

This file was deleted.

Loading

0 comments on commit ffd831e

Please sign in to comment.