2015
DOI: 10.1007/978-3-662-48096-0_43
|View full text |Cite
|
Sign up to set email alerts
|

Behavioral Non-portability in Scientific Numeric Computing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
6
0

Year Published

2016
2016
2021
2021

Publication Types

Select...
3
2
2

Relationship

2
5

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…The average CS reconstruction time of 1.3 minutes on the GPU suggests that this approach may be suitable for in-line reconstruction on the scanner in the clinical environment. The slight difference in image intensity that we found between the 2 computer hardware configurations may be because the CS algorithm was implemented using sequential coding on the CPU and parallel coding on the GPU leading to a different order of operations, and therefore, unequal results (16).…”
Section: Discussionmentioning
confidence: 94%
“…The average CS reconstruction time of 1.3 minutes on the GPU suggests that this approach may be suitable for in-line reconstruction on the scanner in the clinical environment. The slight difference in image intensity that we found between the 2 computer hardware configurations may be because the CS algorithm was implemented using sequential coding on the CPU and parallel coding on the GPU leading to a different order of operations, and therefore, unequal results (16).…”
Section: Discussionmentioning
confidence: 94%
“…This small mean difference is potentially due to the fact that different order of operations could lead to different results in floating-point arithmetic. In our study, the PICS stage was implemented using sequential coding on the CPU and parallel coding on the GPU, which yielded to different order of operations and therefore unequal results [17].…”
Section: Discussionmentioning
confidence: 99%
“…In this paper, instead of solving an optimization problem, we determine input samples that give rise to a suitable "target sensitivity". Requiring this sensitivity to be positive is not enough: differences in the compiler, the computation environment, the available hardware and other unknowns (which impact the precise semantics of floating-point arithmetic [6]) will typically cause some deviations in the output between the client's platform and the cloud. In the absence of an attack, these deviations would show up as false positives.…”
Section: Sensitive Sample Queriesmentioning
confidence: 99%
“…As discussed in Sec. 3.2, this is not quite true: due to platformdependencies of floating-point computations [6], DNN model inference is not deterministic. We address this problem using an empirical non-zero sensitivity detection threshold (Sec.…”
Section: Related Workmentioning
confidence: 99%