Rachel Kurchin
Rachel Kurchin
Nothing should stop someone from having a subtype of `AbstractSystem` that's mutable, and it could be useful for setting up geometries for simulations, especially if they're rather large and the...
Now that AtomsBase is starting to get wider usage, I think a library of examples in the docs would be a good thing to have. Starting this issue to brainstorm...
Currently we have one `D` for number of dimensions and one `S` for the species type. There could be more (e.g. adding `Unitful` types to specify units for length, velocity,...
I'm imagining a primary syntax something like `distance(sys::AbstractSystem, atom_ind_1, atom_ind_2)` that would return the distance between two particles in the structure, and maybe also single-index and no-index options that would...
https://github.com/thchr/Crystalline.jl because this would just be really cool for geometry building etc. ...depending on how in-depth this goes, it could easily end up as a separate package...this issue is mainly...
@cortner suggested this...TBD if it belongs at the top level of the interface...
They're a bit too rigid right now and should ideally be flexible to anything (different types of vectors, tuples, etc.) that might be thrown at them to specify systems.
They were originally `SoASystem` and `AoSSystem` and were changed to the present names. Thoughts?
In lattice-based systems such as those @Gregstrq works on, it will eventually be desirable to support Cartesian and not just linear indexing into `AbstractSystem` objects.
Would it make sense to have this be part of the interface? If so, we would need to be able to dispatch on boundary condition types, which might require rejiggering...