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

Handle range of number types as input #45

Open
rdrclrbh opened this issue Jun 9, 2022 · 3 comments
Open

Handle range of number types as input #45

rdrclrbh opened this issue Jun 9, 2022 · 3 comments

Comments

@rdrclrbh
Copy link
Collaborator

rdrclrbh commented Jun 9, 2022

Right now iVABS trips up on a number with the +E scientific notation. It should be able to handle all types of scientific notation as well as float, int, etc.

@unitasium
Copy link
Contributor

@rdrclrbh Could you provide a more specific example?

@rdrclrbh
Copy link
Collaborator Author

See below snippet from an input file we were trying to use (see +E notation in numbers):

----Start Snippet----
1.5000E+001 -3.2441E+002 -3.3842E+002 -3.4277E+002 -3.4452E+002 -3.4855E+002
3.0000E+001 -2.7749E+002 -2.8507E+002 -2.9738E+002 -3.1440E+002 -3.3317E+002
4.5000E+001 -2.5421E+002 -2.6097E+002 -2.6428E+002 -2.7748E+002 -2.9464E+002
6.0000E+001 -2.8741E+002 -2.8932E+002 -2.8575E+002 -2.8803E+002 -2.8805E+002
7.5000E+001 -3.9833E+002 -3.9218E+002 -3.6880E+002 -3.5165E+002 -3.2998E+002
9.0000E+001 -5.4891E+002 -5.3262E+002 -5.0095E+002 -4.7533E+002 -4.3379E+002
1.0500E+002 -6.8494E+002 -6.6246E+002 -6.2130E+002 -5.8380E+002 -5.2502E+002
1.2000E+002 -7.1714E+002 -6.9096E+002 -6.4268E+002 -6.0656E+002 -5.5474E+002
1.3500E+002 -5.9946E+002 -5.8478E+002 -5.6250E+002 -5.5397E+002 -5.2167E+002
1.5000E+002 -4.5993E+002 -4.5729E+002 -4.5717E+002 -4.6571E+002 -4.6505E+002
1.6500E+002 -4.1422E+002 -4.0990E+002 -4.0834E+002 -4.2041E+002 -4.2403E+002
1.8000E+002 -4.3533E+002 -4.3348E+002 -4.3213E+002 -4.2926E+002 -4.1631E+002
1.9500E+002 -4.6553E+002 -4.6872E+002 -4.6615E+002 -4.5330E+002 -4.3722E+002
2.1000E+002 -4.7143E+002 -4.7391E+002 -4.7273E+002 -4.6533E+002 -4.5172E+002
2.2500E+002 -4.2920E+002 -4.4099E+002 -4.4795E+002 -4.4478E+002 -4.3295E+002
2.4000E+002 -3.3879E+002 -3.7315E+002 -3.9708E+002 -3.9700E+002 -3.8772E+002
2.5500E+002 -2.7935E+002 -3.1212E+002 -3.3584E+002 -3.4405E+002 -3.4346E+002
----End Snippet----

@unitasium
Copy link
Contributor

It seems that this is the file for cross-sectional loading condition. The format can be read by iVABS now is csv, which means that there should be comma , between numbers. I am wondering if this is the actual cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants