We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I get an error when reading the first "G" header line, which is in my iges file:
,,31HOpen CASCADE IGES processor 7.4,13HFilename.iges, G0000001
As a workaround I am replacing this row with a functional line.
As far as I understand you need the right identifier for splitting the line into parameters param_sep = data[2] record_sep = data[6]
param_sep = data[2]
record_sep = data[6]
In my header from Open Cascade export these identifiers are not there. The iges file itself is readable for example in Creo.
Regards, Martin
The text was updated successfully, but these errors were encountered:
I encountered the same issue when loading a file created by recent AutoCAD, which procudes exactly this Header format.
According to http://paulbourke.net/dataformats/iges/IGES.pdf, p. 15 there are four possible formats:
The given example has Form 1.
pyiges wrongly assumes Form 2 and determines the delimiters 3, p instead of ,, ;:
pyiges
3
p
,
;
,,31HOpen CASCADE IGES processor 7.4,13HFilename.iges, G0000001 ^ ^
I provide a solution via #32 feel free to see if You have time.
Sorry, something went wrong.
@akaszynski @msc-turb I think this can be closed
No branches or pull requests
Hi,
I get an error when reading the first "G" header line, which is in my iges file:
As a workaround I am replacing this row with a functional line.
As far as I understand you need the right identifier for splitting the line into parameters
param_sep = data[2]
record_sep = data[6]
In my header from Open Cascade export these identifiers are not there.
The iges file itself is readable for example in Creo.
Regards,
Martin
The text was updated successfully, but these errors were encountered: