Error out of range

massimo · 2021-11-08 13:18:38

Hi,

i'm trying to creat a simultation of a river with a weirs. I created the computational mesh without any errors. For each weirs i create the stringdef of upstream and downstream with the region point "hole" in the middle. In the file model i use the linked boundary wier_linked_costant.

But when i write in basement gives me this error at line in the console -> writing (90099/3) data of type '1' to CellsAll/EdgeSign:

-> out of range (4294967295>=110), in file: N:\src\setup\Substance.cpp on line 188, version v3.1.1
-> ... unfortunately BASEMENT is killed!

i controlled the breaklines and them seems ok, region points and liquind boundaries (weirs included) too.

why does this error occur? how can i resolve this error?

thanks

massimo

Lukas Vonwiller · 2021-11-09 11:37:13

hi Massimo

try to increase the log level, e.g. using -l 5 for the setup.

cheers, Lukas

JBarreiro · 2022-05-24 18:17:07

I am having the very same error: -> out of range (4294967295>=0), in file: N:\src\setup\Substance.cpp on line 188, version v3.1.1

I have checked for material, breaklines or stingfdef issues and I found nothing...

Lukas Vonwiller · 2022-05-25 07:45:57

The main approach when having such problems is to try to simplify your model taking away some parts one by one, so you can locate the problem.

hope this helps!

JBarreiro · 2022-05-25 11:10:11

Lukas Vonwiller wrote:

The main approach when having such problems is to try to simplify your model taking away some parts one by one, so you can locate the problem.
hope this helps!

Thanks for the tip... in fact I tried this approach. I know now that the problem only appears when I introduce Boundaries in the model. I've tried to vary the type of Boudary and its properties but the issue remains.

Any tips on this?!

Kind regards

Lukas Vonwiller · 2022-05-25 11:49:49

good, then you already narrowed down your problem.

What comes to my mind is to check the nodestrings (NS) in the .2dm mesh file (make sure the node numbes are correctly forming a nodestring).

best, Lukas

JBarreiro · 2022-05-25 11:52:57

Lukas Vonwiller wrote:

good, then you already narrowed down your problem.
What comes to my mind is to check the nodestrings (NS) in the .2dm mesh file (make sure the node numbes are correctly forming a nodestring).
best, Lukas

I believe i might know what the issue is. If I am not wrong, in version 2.x of BASEMENT, internal boundaries were closed by default and there was no need to define them (if that was the case) in stringdefs.

Am I wrong, or in versions 3.x of BASEMENT we need to define them as stringdefs and internal closed boundaries?

JBarreiro · 2022-05-26 12:15:30

Hello,

I have been through a set of rectifications on my mesh and model and I still have this problem.

-> out of range (4294967295>=409), in file: N:\src\setup\Substance.cpp on line 188, version v3.1.1

The last console output is:
-> writing (10462/3) data of type '1' to CellsAll/EdgeSign

I would kindly ask if someone can help me on this, do some debbuging... I have no more ideas for what might be causing this...

Thanks

NumericalSam · 2022-05-31 15:11:39

I thought I already left a post here, did someone delete it?
Anyway: maybe check out this article, it's basically the same error: https://forum.basement.ethz.ch/viewtopic.php?id=5438

Edit: I just saw that there is a duplicate thread, that's where I posted the same. I can only suggest what Lukas wrote, eliminate parts of the model until it works and then build it up again.

Last edited by NumericalSam (2022-05-31 15:15:15)

JBarreiro · 2022-05-31 15:14:20

NumericalSam wrote:

I thought I already left a post here, did someone delete it?
Anyway: maybe check out this article, it's basically the same error: https://forum.basement.ethz.ch/viewtopic.php?id=5438

I Sam, I've checked it and I've gone through all those issues. The problems persists. It seems there are a lot of possibilities for that error... But this -> out of range (4294967295>=110) <- should meaning something about it... It's difficult to know without performing a debbuging.

Matthias Bürgler · 2022-05-31 16:07:34

Hi João

I will have a look if you can share you mesh and model setup.

Best regards
Matthias

JBarreiro · 2022-05-31 16:13:56

Matthias Bürgler wrote:

Hi João
I will have a look if you can share you mesh and model setup.
Best regards
Matthias

Thanks Matthias! I've send it through the email option of the forum. Do you confirm the reception?

Many thanks

NumericalSam · 2023-02-07 08:25:52

Is there an update to this issue?

Matthias Bürgler · 2023-04-19 12:38:23

NumericalSam wrote:

Is there an update to this issue?

Are you referring to a specific issue?

If I remember correctly, in JBarreiro's case it was an issue related to the Nodestring definitions in the .2dm file.

Best,
Matthias

JBarreiro · 2023-04-19 14:32:51

Matthias Bürgler wrote:

NumericalSam wrote:
Is there an update to this issue?
Are you referring to a specific issue?
If I remember correctly, in JBarreiro's case it was an issue related to the Nodestring definitions in the .2dm file.
Best,
Matthias

Hi everyone,

Yes, in my case I had a Nodestring wrongly defined

It was: NS 463 5679 5318 5699 5456 5499 464 6002 447 -closed81_2

and should be: NS 463 5679 5318 5699 5456 5499 464 6002 447 closed81_2

Matthias was able to help me only by running in debug mode, since I had a lot of Nodestrings!

User Forum of Software BASEMENT

#1 2021-11-08 13:18:38

Error out of range

#2 2021-11-09 11:37:13

Re: Error out of range

#3 2022-05-24 18:17:07

Re: Error out of range

#4 2022-05-25 07:45:57

Re: Error out of range

#5 2022-05-25 11:10:11

Re: Error out of range

#6 2022-05-25 11:49:49

Re: Error out of range

#7 2022-05-25 11:52:57

Re: Error out of range

#8 2022-05-26 12:15:30

Re: Error out of range

#9 2022-05-31 15:11:39

Re: Error out of range

#10 2022-05-31 15:14:20

Re: Error out of range

#11 2022-05-31 16:07:34

Re: Error out of range

#12 2022-05-31 16:13:56

Re: Error out of range

#13 2023-02-07 08:25:52

Re: Error out of range

#14 2023-04-19 12:38:23

Re: Error out of range

#15 2023-04-19 14:32:51

Re: Error out of range

Board footer