Code indexing in gitaly is broken and leads to code not being visible to the user. We work on the issue with highest priority.

Skip to content
Snippets Groups Projects
Select Git revision
  • 146-rewrite-the-arbitrarydomain-class-2
  • 812-update-multipoletstraight-default-expansion-order-parameter
  • master default protected
  • 810-remove-opal_parser-so-from-branch-opal-2024-1
  • OPAL-2024.1 protected
  • 809-remove-src-pyopal-pyobjects-opal_parser-so
  • 784-get-pyopal-opal-t-working
  • 794-multipolet-cleanup-and-placement
  • 790-opalringdefinition-max_r-min_r-options
  • OPAL-2023.1 protected
  • minimal-opal-for-ippl2.0
  • 756-wrong-class-member
  • 721-error-variable-set-but-not-used
  • origin/745-pyopal-ffa-lattice
  • OPAL-2022.1 protected
  • 327-general-field-map-reader
  • output-plane-element
  • 624-pyopal-build-system
  • OPAL-2021.1 protected
  • 706-bug-with-temporal-monitor-when-running-in-parallel
  • OPAL-2024.1.0
  • OPAL-2022.1.0
  • OPAL-2021.1.0
  • OPAL-2.4.0 protected
  • OPAL-2.2.1 protected
  • OPAL-2.2.0 protected
  • OPAL-21.11.2019
  • OPAL-2.0.2 protected
  • OPAL-15-12-2018
  • OPAL-10-12-2018
  • OPAL-2.0.1 protected
  • OPAL-2.0.0rc2 protected
  • OPAL-2.0.0rc1 protected
  • OPAL-1.6.2 protected
  • OPAL-1.6.1 protected
  • OPAL-1.6.0 protected
  • OPAL-1.9.0 protected
  • OPAL-1.5.2 protected
  • OPAL-1.5.1 protected
  • OPAL-1.4.0 protected
40 results
Compare
kraus's avatar
Merge branch '349-check-that-element-length-is-long-relative-to-a-time-step-2' into 'master'
kraus authored 
Resolve "Check that element length is long relative to a time step"

Closes #349

See merge request !430
3c687690
History
kraus's avatar 3c687690
History
Name Last commit Last update