Not a valid identifier error

Hi,

We are getting a “Solution exception:‘C’ is not a valid Identifier.” Our script is a bit a bit complicated, so I don’t know if it makes sense to upload.

Any idea where to look and what to look for when an error like this appears? Currently, the error is present on our FictitiousBar, BarColumn and Support components.

We are saving data to .csv files using the Colibri aggregator, if that could have influence. All help is appreciated.

Regards :slight_smile:

Update: It seems the problem is fixed by restarting Grasshopper. However it is a bit problematic since we would ideally like to start the simulations and let it run for about 30 hours. Based on out testing it seems like the problem arises sometime during the run time.

Hi @AKiaer

Can you make sure to have the latest API installed?
I can not reproduce the bug unfortunately.

Can you also try to create only ONE FictitiousBar, BarColumn and Support in a .gh file and see if the error raise?

Hi Marco,

Yep, we have the latest version.

I cannot reproduce the bug with one FictitiousBar, BarColumn and Support. However, we have found that the error occurs during the simulations. We are running modal analysis on about 15.000 structures, and the bug starts occurring about half way through, and the FictitiousBars and BarColumns are not generated as the components return an error.

We will try to reduce the number of inputs to our model to see if simplifying the grasshopper file will solve the issue, will provide updates.

Hi @AKiaer

Can you internalise the curve input and see if the error still happen?
In that case, you can send me those geometry.

However, if the error appears during the analysis, it is something that we will need to raise to FEM-Design

Hi @MarcoPelle

If we internalise the data (right click on the e.g. the FictitiousBar component) the script is no longer parametric, right? It seems this way.

The error appears after about 3000 analysis in my latest tests. Should I upload the entire script or just the geometry for the FictitiousBar?

@AKiaer
Internalising the data is just to allow me to see if there is something wrong in the input curve :slight_smile:

Feel free to upload the geometry (not the FEM element) of the components that raise the error.

If I can not reproduce, we can set up a call.