To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.dev.org.ldrawOpen lugnet.cad.dev.org.ldraw in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / Organizations / LDraw / 1527
1526  |  1528
Subject: 
Parts Tracker - Using L3P-check to scan submitted files
Newsgroups: 
lugnet.cad.dev.org.ldraw
Date: 
Wed, 17 Oct 2001 17:39:47 GMT
Viewed: 
232 times
  
Hey y'all-

I'm just sort of starting to get to adding L3P-check'ing to the Parts
Tracker submit function.  I took a look at the documented messages, and
tried to sort them out according to whether or not any particular error was
cause to reject a submitted file.  I've listed my results below.

What do you all think about this?  Is this list alright?

Steve

L3P -check Messages
=============================================================================
(the number on the front of the line is the warning level required to check
for the specific condition)

Errors that should be rejected:

0 Bad line                                 Line does not begin with a number
0 Unknown line type                        Linetype not 0..5
0 %d arguments expected                    Wrong number of numbers for linetype
0 Bad color                                Bad syntax of color in line
0 Unknown color, using 7                   Color not in valid range
1 Identical vertices                       Two or more vertices are identical
1 Collinear vertices (%g)                  Vertices lie on a line (linetype 3)
1 Collinear vertices 012 (%g)              Vertices lie on a line (linetype 4)
1 Collinear vertices 013 (%g)              Vertices lie on a line (linetype 4)
1 Collinear vertices 023 (%g)              Vertices lie on a line (linetype 4)
1 Collinear vertices 123 (%g)              Vertices lie on a line (linetype 4)

Not appropriate for part files (also cause rejection):

0 Sorry, cannot handle color %d, using 15  Color 16 or 24 specified for
                                           light.dat
0 Unknown color, using 15                  Color of light not in valid range
0 Illegal syntax                           of TRANSLATE/ROTATE/SCALE/TRANSFORM
0 Zero vector                              in ROTATE meta command
0 %s END expected                          of TRANSLATE/ROTATE/SCALE/TRANSFORM
0 END not expected                         of TRANSLATE/ROTATE/SCALE/TRANSFORM
0 FILE %s already read                     MPD subfile has same name as
                                           another file
0 LDraw command(s) preceded this line      Valid commands before first 0 FILE


Errors, but should they cause rejection?:

2 Vertices not coplanar (%g)               Only if -det/-dist option
1 Identical to a previous line             Line has been seen before (L3P16)
1 Identical to line %u                     Line has been seen before (L3P32)

BFC Warnings (don't reject):

0 Singular matrix                          Typically too many zeros
2 Row %d all zeros                         Zero row in matrix
2 Y column all zeros                       Zero y column in matrix
0 Singular matrix (unfixable)              L3P cannot fix matrix
1 Bad vertex sequence, 0312 used           Bow-tie in linetype 4
1 Bad vertex sequence, 0132 used           Bow-tie in linetype 4

Warnings (don't reject):

0 Color 24 illegal for this line type, using 16  Color 24 not valid for
                                           linetype 1,3,4
1 Lines should not use color 16            Color 16 not valid for linetype 2,5
3 Comment lines should have space after 0  Ill-formatted comment like "01 ..."



Message has 3 Replies:
  Re: Parts Tracker - Using L3P-check to scan submitted files
 
(...) Looks good. (...) I have used the phrase "0 end of subpart", "0 end of file", etc in some of the parts I have made. Will these get rejected? I usually always try to keep them lowercase. (...) I'm not sure about this one. I feel that new parts (...) (23 years ago, 18-Oct-01, to lugnet.cad.dev.org.ldraw)
  Re: Parts Tracker - Using L3P-check to scan submitted files
 
Steve: (...) [...] Seems okay. (...) [...] Seems okay. (...) I would say yes. The last two definitely should, since they indicate unneeded resource use. The first one should really be split in to two triangles, if it really is intended to be (...) (23 years ago, 18-Oct-01, to lugnet.cad.dev.org.ldraw)
  Re: Parts Tracker - Using L3P-check to scan submitted files
 
I finally formatted the material about L3P messages vs. part files and put it under the reference area of the Parts Tracker. (URL) If you don't have L3P installed on your computer, you can check your part files at: (URL) This script must upload your (...) (22 years ago, 8-Feb-02, to lugnet.cad.dev.org.ldraw)

7 Messages in This Thread:



Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR