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

Error of "znaupd: starting vector is zero, try rerunning?" #105

Closed
Brch opened this issue Jul 28, 2022 · 1 comment · Fixed by #106 or #139
Closed

Error of "znaupd: starting vector is zero, try rerunning?" #105

Brch opened this issue Jul 28, 2022 · 1 comment · Fixed by #106 or #139
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Brch
Copy link

Brch commented Jul 28, 2022

Issue description

When running with the Arnoldi solver in some cases, I get an error:

ERROR   | znaupd: starting vector is zero, try rerunning?
ERROR STOP 

sometimes, re-running it indeed works as suggested, but usually it does not and the problem cannot be computed at all.

Bug report

With no changes to the code, with a parameter file that reads:

&gridlist
  gridpoints = 250
  x_start = 0.0
  x_end = 0.1
/

&equilibriumlist
  equilibrium_type = "rayleigh_taylor"
/

&solvelist
  solver = "arnoldi"
  arpack_mode = "general"
  number_of_eigenvalues = 10
  which_eigenvalues = "LI"
  maxiter = 16000
  ncv = 400
/

&savelist
  write_eigenfunctions = .true.
  show_results = .true.
/
&paramlist
  k2 = 1
  k3 = 0
/

Actual result

  INFO    | the state vector is set to [rho, v1, v2, v3, T, a1, a2, a3]
  WARNING | overriding x_end with 0.10000000
  WARNING | standard equilibrium conditions not satisfied!
            location of largest discrepancy (1): x = 0.02396385
            value of largest discrepancy (1): 0.13546941E-11
            amount of nodes not satisfying criterion (1): 984
 
  INFO    | ---------------------------------------------
                          << Grid settings >>
            geometry           : Cartesian
            grid start         : 0.00000000
            grid end           : 0.10000000
            gridpoints (base)  : 250
            gridpoints (Gauss) : 996
            gridpoints (matrix): 4000
                      << Equilibrium settings >>
            equilibrium    : rayleigh_taylor
            wave number k2 : 1.00000000
            wave number k3 : 0.00000000
            default params : True
                        << Physics settings >>
            flow               : True
            external gravity   : True
            radiative cooling  : False
            thermal conduction : False
            resistivity        : False
            viscosity          : False
            hall mhd           : False
                        << Solver settings >>
            solver      : arnoldi
            ARPACK mode : general
            number of eigenvalues : 10
            which eigenvalues     : LI
                        << DataIO settings >>
            datfile name         : datfile
            output folder        : output
            write matrices       : False
            write eigenfunctions : True
            write derived eigenfunctions : False
            write eigenfunction subset : False
            ---------------------------------------------
 
  INFO    | solving eigenvalue problem...
  WARNING | Arnoldi: maxiter (16000) below recommended 10*N (40000)
  ERROR   | znaupd: starting vector is zero, try rerunning?
ERROR STOP 
@n-claes n-claes added the bug Something isn't working label Jul 28, 2022
@n-claes
Copy link
Owner

n-claes commented Oct 3, 2022

This problem seems to be an issue with ARPACK itself and not on our end, for some reason the forcing of the starting vector into the range of OP returns zero. I think I found a workaround though, in the referenced commit above I modified the ARPACK configuration to use a manually initialised starting vector using a (-1, 1) random uniform distribution and that seems to solve (all) issues. I've also seen this problem popping up in our unit tests every so often, that seems to be fixed as well now.

The fix will soon be available on the develop branch.

@n-claes n-claes self-assigned this Oct 3, 2022
@n-claes n-claes added this to the Legolas 2.0 milestone Oct 3, 2022
@n-claes n-claes linked a pull request Oct 4, 2022 that will close this issue
11 tasks
@n-claes n-claes closed this as completed in d22cf73 May 5, 2023
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.

2 participants