Unofficial File parts/30367cps8.dat
part image
File Header:
0 Cylinder  2 x  2 with Dome Top with SW Dark Blue / R2-D2 (2013) Pattern
0 Name: 30367cps8.dat
0 Author: Franklin W. Cain [fwcain]
0 !LDRAW_ORG Unofficial_Part
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt

0 BFC CERTIFY CCW

0 !KEYWORDS Star Wars, droid, astromech, minifig
0 !KEYWORDS Artoo-Detoo, R2, Artoo, blue droid

0 !CMDLINE -c179


Status:
4 subfiles aren't certified. (SSSSN)
Size: 2835 bytes
Reviewers' certifications:
UR=novote
fwcain=novote
Required (unofficial) subfiles:
Related (unofficial) subfiles:
(none)
File reviews and updates:
At Mon Apr 29 06:50:01 2019, the file was initially submitted.
Submitted by: fwcain
At Tue Apr 30 21:45:01 2019, the following review was posted:

Reviewer: MagFors
Certification: hold
Comments:

All comments have a bad format. Missing //
Empty comments should be removed. 0

"If a line is non-empty, the first token must be an integer from the list of valid Line Type numbers."
http://www.ldraw.org/article/218.html#parsing

Why does the files end with a 0 NOFILE?

All of these errors are removed if you use Datheader.
The same errors are present in all your new files.

At Tue Apr 30 23:10:01 2019, a new version of the file was submitted.
Submitted by: fwcain
Comments:
Fixed comments.
Existing certification-votes were deleted.
At Sat May 4 15:50:01 2019, a new version of the file was submitted.
Submitted by: fwcain
At Sun May 5 07:10:01 2019, the following review was posted:

Reviewer: MagFors
Certification: hold
Comments:

Don't know what you changed, but you still need to remove the empty space in the beginning of every line.
A line of code is not allowd to beginn with a Space.

At Sun May 5 10:00:02 2019, the following review was posted:

Reviewer: fwcain
Certification: novote
Comments:
Citation, please...
At Sun May 5 10:05:01 2019, the following review was posted:

Reviewer: fwcain
Certification: certify
Comments:
Actually, I just checked, and you're wrong...

This article:
http://www.ldraw.org/article/218.html
...clearly states that the use of white-spaces (i.e. blank spaces) is permitted.

Please remove your Hold vote, as your citation is in error. Thank you...
At Sun May 5 11:30:01 2019, the following review was posted:

Reviewer: MagFors
Certification: hold
Comments:

Am I not reading this line correct?
"If a line is non-empty, the first token must be an integer from the list of valid Line Type numbers."
http://www.ldraw.org/article/218.html#parsing

There's a difference between Space and white-space. Right?
We're allowed to add an empty line (white-space) between two lines of code,
but we're not allowed to begin a line of code with a Space (that big key at the bottom of your keyboard).

At Mon May 6 02:20:01 2019, the following review was posted:

Reviewer: fwcain
Certification: certify
Comments:
(quote):
Each command consists of optional leading whitespace ...

Each command CAN consist of leading blank spaces, in the same line.
At Mon May 6 02:25:02 2019, the following review was posted:

Reviewer: fwcain
Certification: certify
Comments:
And in the part you quoted, they use the word TOKEN, not CHARACTER. If the first CHARACTER must be one of the integers allowed, then you would be correct. But they used the word TOKEN instead.

At Mon May 6 13:55:03 2019, the following review was posted:

Reviewer: UR
Certification: hold
Comments:
In one point I'm with you:
" Each command consists of optional leading whitespace followed by whitespace-delimited tokens."
..... an unlucky formulated explanation.

But ...Magnus is absolutely right:
"If a line is non-empty, the first token must be an integer from the list of valid Line Type numbers. This number dictates further parsing of tokens for that line."

....and by the way:
Self-certification always leaves a slightly unpleasant odor -
benevolently said.

At Mon May 6 15:15:01 2019, the following review was posted:

Reviewer: MagFors
Certification: hold
Comments:

Thank you, Ulrich. I was beginning to question my skills in reading english....

It doesn't matter if it is white-space, a space, a character or a token.
A line of code is only permitted to begin with 1, 2, 3, 4 or 5. Nothing else.

At Mon May 6 17:25:01 2019, the following review was posted:

Reviewer: OrionP
Certification: hold
Comments:
Please move this argument to the forums. The PT is not the appropriate place to debate. Holding until this is resolved properly.

At Thu May 9 09:35:01 2019, a new version of the file was submitted.
Submitted by: fwcain
Comments:
removed leading spaces

Existing certification-votes were deleted.
At Thu May 9 20:20:01 2019, the following review was posted:

Reviewer: MagFors
Certification: hold
Comments:

Hi Frank,
Thank you for fixing this, and I'm sorry to have to hold vote it again.

Some of the keywords are used in the description and have to be removed.
And there is also some trailing zeros in the code, like: 10.4000
Some of the subfiles contain colinear triangles.

Which editor do you use?
Non of these errors are present in the original file, 30367cps0

Could you please also fix the same error in the subfiles, and the other two parts?

Do you use Datheader?
It can auto correct all of these errors.
I'm using it to find them.
At Fri May 10 07:05:01 2019, the following review was posted:

Reviewer: fwcain
Certification: novote
Comments:
1) If you don't like some of the keywords, how about you specify which ones, and include a REASON as to why they offend you -- I can not read minds. As far as I am concerned, EVERY SINGLE ONE of those keywords matters to the droid character whose head this pattern represents.

2) Show me ANY WHERE in the rules that trailing zeroes are worthy of a hold.

3) While a part file is under review, such things (as keywords and trailing zeroes (and leading spaces, too, for what that's worth) are not SUPPOSED to be worthy of a hold, as they can be Admin-fixed, once the part file is cleared for release. Posting a hold vote for such trivial, petty reasons just angers some people. And doing so repeatedly just shows contempt for the person in question, as far as I am concerned.

4) My given name has eight letters, not five.
At Fri May 10 15:30:01 2019, the following review was posted:

Reviewer: MagFors
Certification: hold
Comments:

I'm sorry, Franklin.

I'm Hold voting for one reason.
"R2-D2" is both in the description and in the list of keywords.
http://www.ldraw.org/article/340.html#category
"Words and terms from the part name are not allowed; neither is the part number."

Trailing zero's
http://www.ldraw.org/article/512.html#format
"Trailing zeros must be removed (ie 1.5 not 1.500)."

As far as I know, Admin will not correct "errors" in the code.
It must be done by the author.

Again, I'm sorry if I offended you by misspelling your name.

At Sat May 11 00:20:02 2019, a new version of the file was submitted.
Submitted by: fwcain
Comments:
1) Removed "R2-D2" from Keywords.

2) To the best of my knowledge and belief, the only number that had trailing zeroes was the value 10.4 ("10.4000"), and all such instances of that value have been truncated accordingly.
Existing certification-votes were deleted.
At Sat May 11 16:45:01 2019, the following review was posted:

Reviewer: UR
Certification: novote
Comments:
I would like to recommend you DATHeader .... as an official reviewer tool .... the program continues to show 3 small problems .... :

1 WARNING Maybe leading spaces in part description.

2 WARNING Too much empty lines at the end of the file.

3 ERROR Leading or trailing zeros found.

.... which to my knowledge .... only is usable in windows .... so far as an information ... if you work with a MAC....


https://ldraw.heidemann.org/index.php?page=datheader


furthermore:

Line 39 and 40 showing flat subfiles scaled in Y direction

unmatched vertices and T-junctions here:

2 4 11.369 11.168 15.141 12.699 11.168 14.251
2 4 12.961 14.332 14.6415 12.6985 11.168 14.251
2 4 12.961 14.332 14.641 11.631 14.332 15.531
2 4 12.699 11.168 14.251 12.83 12.75 14.446
2 4 12.83 12.75 14.446 12.961 14.332 14.641
2 4 11.631 14.332 15.531 10.301 14.332 16.421
2 4 10.301 14.332 16.421 10.17 12.75 16.226
2 4 10.17 12.75 16.226 10.039 11.168 16.031
2 4 10.3015 14.332 16.421 12.961 14.332 14.6415
2 4 12.6985 11.168 14.251 10.039 11.168 16.0305
2 4 10.039 11.168 16.0305 10.3015 14.332 16.421
2 4 10.039 11.168 16.031 11.369 11.168 15.141


please check this by yourself in LDPartEditor using the tools T-junctionFinder and Edger2


At Sun May 12 14:00:02 2019, the following review was posted:

Reviewer: fwcain
Certification: novote
Comments:
There is a message thread at the Forums for discussing this group of related files...
https://forums.ldraw.org/thread-23370-post-31978.html

Thanks,
Franklin