Opened 4 years ago

Last modified 4 years ago

#1691 confirmed defect

Time integration of grid arrays with MoL is incorrect when there is more than one component per process

Reported by: Ian Hinder Owned by:
Priority: major Milestone:
Component: Cactus Version: development version
Keywords: Cc:


MoL integrates its variables in local mode (loop over components), and grid arrays are stored per process, so MoL integrates evolved grid arrays multiple times, leading to wrong results, if there is more than one component per process. I believe the best solution is to move integration of grid arrays into a separate function, scheduled in a different mode (MoL_AddArrays), either global or local. However, a quick short-term "fix" is to copy the check that Slab makes that it is running with only a single component per process. Users can then work around the problem by running on more processes, and won't get silent wrong results.

Attachments (0)

Change History (1)

comment:1 Changed 4 years ago by Ian Hinder

Priority: minormajor
Status: newconfirmed

Setting priority to major, since this can lead to wrong results if MoL is used to integrate grid arrays, which it claims to be able to do. I have several thorns which do this.

Modify Ticket

Change Properties
Set your email in Preferences
as confirmed The ticket will remain with no owner.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from (none) to the specified user.
The owner will be changed from (none) to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.