Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: don't use subset to check if interval vector is in the interior of the other #93

Closed
lucaferranti opened this issue Sep 17, 2021 · 2 comments · Fixed by #94
Closed
Labels
bug Something isn't working

Comments

@lucaferranti
Copy link
Member

Bug description

Verified floating point algorithms (such as epsilon inflation) need to check that a vector is in the interior of the other. Currently, this is done by all(x .⊂ y), but that checks it is a proper subset.

Minimum (non-)working example

Expected behavior

use all(isinterior.(x, y)) instead.

Version info

  • IntervalLinearAlgebra.jl version: 0.1.1
  • System information:
Julia Version 1.6.1
Commit 6aaedecc44 (2021-04-23 05:59 UTC)
Platform Info:
  OS: Windows (x86_64-w64-mingw32)
  CPU: Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-11.0.1 (ORCJIT, skylake)
Environment:
  JULIA_EDITOR = code.cmd -g

Related issues

See related issue in IntervalArithmetic.jl here

Additional information

Add any other useful information

@lucaferranti lucaferranti added the bug Something isn't working label Sep 17, 2021
@lucaferranti
Copy link
Member Author

for the verified eigenvalues this requires a PR in IA as currently isinterior is not defined for complex intervals.

julia> a = (1..2) + (2..3)*im
[1, 2] + [2, 3]im

julia> isinterior(a, a)
ERROR: MethodError: no method matching isinterior(::Complex{Interval{Float64}}, ::Complex{Interval{Float64}})
Stacktrace:
 [1] top-level scope
   @ REPL[9]:1

@lucaferranti
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant