Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
SWIFTsim
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SWIFT
SWIFTsim
Commits
8d8be86e
Commit
8d8be86e
authored
8 years ago
by
Matthieu Schaller
Browse files
Options
Downloads
Patches
Plain Diff
Correctly initialise the engine in the FFT test.
parent
d92cb31d
No related branches found
No related tags found
1 merge request
!340
Split the drift into hydro and gravity drift tasks. Implement FFT task and dependencies
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/testFFT.c
+5
-2
5 additions, 2 deletions
tests/testFFT.c
with
5 additions
and
2 deletions
tests/testFFT.c
+
5
−
2
View file @
8d8be86e
...
...
@@ -47,7 +47,9 @@ int main() {
/* Make one particle */
int
nr_gparts
=
1
;
struct
gpart
*
gparts
=
NULL
;
posix_memalign
((
void
**
)
&
gparts
,
64
,
nr_gparts
*
sizeof
(
struct
gpart
));
if
(
posix_memalign
((
void
**
)
&
gparts
,
64
,
nr_gparts
*
sizeof
(
struct
gpart
))
!=
0
)
error
(
"Impossible to allocate memory for gparts."
);
bzero
(
gparts
,
nr_gparts
*
sizeof
(
struct
gpart
));
gparts
[
0
].
x
[
0
]
=
0
.
3
;
...
...
@@ -73,7 +75,8 @@ int main() {
engine
.
s
=
&
space
;
space
.
e
=
&
engine
;
engine
.
time
=
0
.
1
f
;
engine
.
ti_current
=
8
;
engine
.
ti_current
=
0
;
engine
.
ti_old
=
0
;
engine
.
max_active_bin
=
num_time_bins
;
engine
.
gravity_properties
=
&
gravity_properties
;
engine
.
nr_threads
=
1
;
...
...
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