-
Notifications
You must be signed in to change notification settings - Fork 16
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
Segment tag number error #47
Comments
Can you provide the .NEC file which generated this error? |
Calculations cannot run unless the .NEC file has been saved. Thus, as far as I can tell, it is not possible to get this error unless the file has been saved. If you believe this assessment is incorrect, then please provide a step-by-step procedure to generate the error in such way that the file on disk differs from the file in the editor. |
This file, generated within the application, produces "Segment tag number error": Moxon240503.nec. [attached with ".txt" extension. Apparently, it did save, even though when I clicked the Save icon, I got the error, implying that the command had not completed. If I had looked at the file characteristics, I would have seen that the OS knew it had been recently modified. Another file, created outside the application, produces "Segment data error, zero-length line? See console." Moxon240504.nec If we can capture this class of issue--stupid user tricks and obscure error messages--we can add text to the user manual written once/read many until the app or the error message changes. This is work I for which I would respond to a Help Wanted ad. |
Unfortunately NEC2 tries to parse your input and then calculates segment sizes, so it cannot always produce a meaningful error (this is an NEC2 problem, not an xnec2c problem per se). If you run
Additionally, you have two excitations (
The official an EC to documentation is available here: These are the references that I used to diagnose the errors that your geometry generated:
You are correct in that the graphical error could be more meaningful by also displaying the console errors in graphical output. If the Lines 91 to 93 in 994927d
I opened issue #48 if that is something that you would like to tackle with a pull request, as I do not know when I will get to that. I am of course open to any means of making this program more accessible to users and improvements are welcome. |
This attempts to address #47 by making it more clear what the problem may be.
This attempts to address #47 by making it more clear what the problem may be.
Update docs with troubleshooting hints for "Segment tag number error."
While the underlying user error may be common to all NEC2 applications, the error message appears to be unique. A sentence or two in the user manual is easy; a hint in the application error message might be more work.
In the mean time, the user is prevented from saving his or her work, which may be substantial.
The text was updated successfully, but these errors were encountered: