Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
pairs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
software
pairs
Commits
5fcd1e2f
Commit
5fcd1e2f
authored
2 years ago
by
Rafael Ravedutti
Browse files
Options
Downloads
Patches
Plain Diff
Update agenda
Signed-off-by:
Rafael Ravedutti
<
rafaelravedutti@gmail.com
>
parent
7ae76a36
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
log/logbook_RR.md
+11
-11
11 additions, 11 deletions
log/logbook_RR.md
with
11 additions
and
11 deletions
log/logbook_RR.md
+
11
−
11
View file @
5fcd1e2f
...
@@ -20,21 +20,21 @@ The Agenda section is a scratchpad area for planning and Todo list
...
@@ -20,21 +20,21 @@ The Agenda section is a scratchpad area for planning and Todo list
# Agenda
# Agenda
*
Use variables to accumulate forces (reduction)
*
Use variables to accumulate forces (reduction)
*
Express simulation specific kernels (cell lists, PBC, neighbor lists, comm) in a cleaner way with new syntax
*
DEM/Test case
*
MPI support
*
waLBerla as backend (Load-Balancing)
*
GPU support
*
Coupling interfaces
*
LLVM support
*
OpenMP support
*
OpenMP support
*
LLVM support
*
Express simulation specific kernels (cell lists, PBC, neighbor lists, comm) in a cleaner way with new syntax
Maybes
*
Common subexpression elimination (CSE)
*
Common subexpression elimination (CSE)
*
Analyze generated code by backend compilers to see which cases we really need to manage
*
Analyze generated code by backend compilers to see which cases we really need to manage
*
waLBerla as backend (Load-Balancing)
*
Provide test cases (LJ, EAM, DEM, Configurational Forces + Energy Minimization, ...)
*
Separate performance strategies from code (parallelism, gathering), allow to experiment different strategies
*
Separate performance strategies from code (parallelism, gathering), allow to experiment different strategies
*
Coupling interfaces
*
LAMMPS as backend
*
Maybes:
*
Many-body potentials code generation
*
LAMMPS as backend
*
Long-range forces
*
Many-body potentials code generation
*
Long-range forces
<!--  -->
<!--  -->
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment