Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
fslpy
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Analyze
Contributor analytics
CI/CD 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
FSL
fslpy
Commits
3d9fd95a
Commit
3d9fd95a
authored
5 years ago
by
Paul McCarthy
Browse files
Options
Downloads
Patches
Plain Diff
TEST: Test that gifti.relatedFiles doesn't return dupes
parent
efcc99f9
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
tests/test_gifti.py
+7
-0
7 additions, 0 deletions
tests/test_gifti.py
with
7 additions
and
0 deletions
tests/test_gifti.py
+
7
−
0
View file @
3d9fd95a
...
...
@@ -224,6 +224,7 @@ def test_relatedFiles():
assert
len
(
gifti
.
relatedFiles
(
badname
))
==
0
assert
len
(
gifti
.
relatedFiles
(
'
nonexistent
'
))
==
0
llisting
=
[
op
.
join
(
td
,
f
)
for
f
in
listing
]
lsurfaces
=
[
op
.
join
(
td
,
f
)
for
f
in
lsurfaces
]
rsurfaces
=
[
op
.
join
(
td
,
f
)
for
f
in
rsurfaces
]
lrelated
=
[
op
.
join
(
td
,
f
)
for
f
in
lrelated
]
...
...
@@ -236,6 +237,12 @@ def test_relatedFiles():
result
=
gifti
.
relatedFiles
(
s
)
assert
sorted
(
rrelated
)
==
sorted
(
result
)
exp
=
lsurfaces
+
lrelated
exp
=
[
f
for
f
in
exp
if
f
!=
lsurfaces
[
0
]]
result
=
gifti
.
relatedFiles
(
lsurfaces
[
0
],
ftypes
=
gifti
.
ALLOWED_EXTENSIONS
)
assert
sorted
(
exp
)
==
sorted
(
result
)
TEST_VERTS
=
np
.
array
([
[
0
,
0
,
0
],
[
1
,
0
,
0
],
...
...
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