Skip to content

magneticParticles3d

OpenLB – Open Source Lattice Boltzmann Code › Forums › on OpenLB › Bug Reports › magneticParticles3d

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • April 26, 2020 at 5:40 pm #4935
    Bhuttu
    Participant

    I am using UBUNTU 18.04 (LTS) and when I compiled magneticParticle3d, I got this even though the program was still running.
    I am using gcc compiler 7.5
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,55,19) ~ (0.00284,0.00104,0.00086), in direction 5
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,20) ~ (0.00284,0.00106,0.00088), in direction 6
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,18) ~ (0.00284,0.00106,0.00084), in direction 7
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,20) ~ (0.00284,0.00106,0.00088), in direction 1
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,57,20) ~ (0.00284,0.00108,0.00088), in direction 4
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,55,20) ~ (0.00284,0.00104,0.00088), in direction 5
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,21) ~ (0.00284,0.00106,0.0009), in direction 6
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,19) ~ (0.00284,0.00106,0.00086), in direction 7
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,21) ~ (0.00284,0.00106,0.0009), in direction 1
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,57,21) ~ (0.00284,0.00108,0.0009), in direction 4
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,55,21) ~ (0.00284,0.00104,0.0009), in direction 5
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,22) ~ (0.00284,0.00106,0.00092), in direction 6
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,20) ~ (0.00284,0.00106,0.00088), in direction 7
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,22) ~ (0.00284,0.00106,0.00092), in direction 1
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,57,22) ~ (0.00284,0.00108,0.00092), in direction 4
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,55,22) ~ (0.00284,0.00104,0.00092), in direction 5
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,23) ~ (0.00284,0.00106,0.00094), in direction 6
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,21) ~ (0.00284,0.00106,0.0009), in direction 7
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,56,23) ~ (0.00284,0.00106,0.00094), in direction 1
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,57,23) ~ (0.00284,0.00108,0.00094), in direction 4
    [BoundaryConditionInstantiator3D] ERROR: no boundary found at (68,55,23) ~ (0.00284,0.00104,0.00094), in direction 5

    April 26, 2020 at 7:40 pm #4936
    mathias
    Keymaster

    That is related to Bouzid BC. It sets Bounce Back instead. Therefore, it is working. We will fix that minor bug in the next release.

    Best
    Mathias

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.