Official File parts/30367cps8.dat
Part Attributes:
Base Part: 30367c.dat
File Header:
0 Cylinder 2 x 2 with Dome Top with Lavender Dots, Dark Blue R2-D2 Pattern
0 Name: 30367cps8.dat
0 Author: Franklin W. Cain [fwcain]
0 !LDRAW_ORG Part UPDATE 2024-04
0 !LICENSE Licensed under CC BY 4.0 : see CAreadme.txt
0 BFC CERTIFY CCW
0 !KEYWORDS Artoo, Artoo-Detoo, astromech, blue droid, BrickLink 553pb017b
0 !KEYWORDS droid, minifig, R2, Rebrickable 30367cpr1000, Set 75136, set 75159
0 !KEYWORDS Set 75168, set 75214, Star Wars
0 !HISTORY 2024-05-28 [OrionP] Official Update 2024-04
Show contents
1 272 0 0 0 1 0 0 0 1 0 0 0 1 s\30367ps0s01.dat
1 272 0 0 0 1 0 0 0 1 0 0 0 1 s\30367ps0s02.dat
1 272 0 0 0 1 0 0 0 1 0 0 0 1 s\30367ps0s03.dat
1 16 0 0 0 1 0 0 0 1 0 0 0 1 s\30367ps0s04.dat
0 // secondary eye
4 31 1.8077 11.1602 -18.9189 1.1786 11.128 -19.0392 0.5985 11.3732 -19.1912 2.3897 11.4646 -18.8485
3 31 2.3897 11.4646 -18.8485 0.5985 11.3732 -19.1912 0.1557 11.8586 -19.3516
4 31 2.8365 11.9954 -18.8388 2.3897 11.4646 -18.8485 0.1557 11.8586 -19.3516 0 12.2845 -19.4461
3 31 3.0797 12.6715 -18.8912 2.8365 11.9954 -18.8388 0 12.2845 -19.4461
4 31 -0.0798 13.2285 -19.5712 0 13.4503 -19.6199 0 12.2845 -19.4461 -0.0825 12.5101 -19.4635
4 31 3.0797 12.6715 -18.8912 0 12.2845 -19.4461 0 13.4503 -19.6199 3.0823 13.3898 -18.9978
4 31 0.1634 13.9045 -19.6551 2.8441 14.0413 -19.1423 3.0823 13.3898 -18.9978 0 13.4503 -19.6199
4 31 0.6101 14.4353 -19.6454 2.4013 14.5267 -19.3027 2.8441 14.0413 -19.1423 0.1634 13.9045 -19.6551
4 31 1.1922 14.7399 -19.575 1.8212 14.7719 -19.4547 2.4013 14.5267 -19.3027 0.6101 14.4353 -19.6454
0 // plug lights
4 322 -8.1727 11.7 -17.3751 -9.2421 11.7 -16.6603 -9.277 12.2 -16.725 -8.2034 12.2 -17.4425
4 322 -8.2955 13.7 -17.645 -9.3814 13.7 -16.9191 -9.4164 14.2 -16.9838 -8.3262 14.2 -17.7124
0 // thick-lined box
1 31 11.5 12.75 15.336 1.33 0 0.131 0 1 1.582 -0.89 0 0.195 4-4disc.dat
1 16 11.5 12.75 15.336 1.33 0 0.131 0 1 1.582 -0.89 0 0.195 4-4ndis.dat
3 16 7.3349 10.4 17.7062 10.039 11.168 16.030 10.17 12.75 16.226
3 16 7.3349 10.4 17.7062 11.369 11.168 15.141 10.039 11.168 16.030
3 16 7.3349 10.4 17.7062 13.4478 10.4 13.6205 11.369 11.168 15.141
3 16 13.4478 10.4 13.6205 12.698 11.168 14.251 11.369 11.168 15.141
3 16 13.4478 10.4 13.6205 12.83 12.75 14.446 12.698 11.168 14.251
3 16 13.4478 10.4 13.6205 13.9391 15.1001 14.1192 12.83 12.75 14.446
3 16 13.9391 15.1001 14.1192 12.961 14.332 14.642 12.83 12.75 14.446
3 16 13.9391 15.1001 14.1192 11.631 14.332 15.531 12.961 14.332 14.642
3 16 13.9391 15.1001 14.1192 7.6027 15.1001 18.3540 11.631 14.332 15.531
3 16 7.6027 15.1001 18.3540 10.302 14.332 16.421 11.631 14.332 15.531
3 16 7.6027 15.1001 18.3540 10.17 12.75 16.226 10.302 14.332 16.421
3 16 7.6027 15.1001 18.3540 7.3349 10.4 17.7062 10.17 12.75 16.226
4 16 7.3349 10.4 17.7062 7.6027 15.1001 18.354 4.9578 15.1 18.8801 4.7829 10.4 18.2138
0 // big slot within panel
4 0 -14.0997 12.95 13.4021 -13.9922 11.95 13.2997 -13.7148 11.95 13.7148 -13.8203 12.95 13.8203
4 0 -13.8203 12.95 13.8203 -13.7148 11.95 13.7148 -7.4232 11.95 17.9198 -7.4802 12.9501 18.0577
4 0 -7.1999 12.9501 18.1132 -7.4802 12.9501 18.0577 -7.4232 11.95 17.9198 -7.145 11.9501 17.975
0 // all else
1 16 0 19.3 0 20 0 0 0 0.7 0 0 0 20 4-4cyli.dat
1 16 0 16 0 -7.653669 0 -18.477591 0 0.7 0 18.477591 0 -7.653669 3-4cyli.dat
1 16 0 0 0 1 0 0 0 1 0 0 0 1 s\30367cs01.dat
Status:
Official
Unofficial parents
Part Events:
Archived Part Events:
2019-04-29 06:50:01
Fixed comments.
Existing certification-votes were deleted.
Existing certification-votes were deleted.
2019-05-04 15:50:01
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.
2019-05-05 10:00:02
Citation, please...
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...
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...
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).
(quote):
Each command consists of optional leading whitespace ...
Each command CAN consist of leading blank spaces, in the same line.
Each command consists of optional leading whitespace ...
Each command CAN consist of leading blank spaces, in the same line.
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.
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.
" 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.
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.
Please move this argument to the forums. The PT is not the appropriate place to debate. Holding until this is resolved properly.
removed leading spaces
Existing certification-votes were deleted.
Existing certification-votes were deleted.
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.
2019-05-10 07:05:01
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.
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.
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.
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.
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.
2019-05-11 16:45:01
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
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
2019-05-12 14:00:02
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
https://forums.ldraw.org/thread-23370-post-31978.html
Thanks,
Franklin
Line 39: Flat subfile is scaled in flat direction 1 100 11.5 12.75 15.336 1.33 -0.88 0.131 0 0.235 1.582 -0.89 -1.315 0.195 4-4disc.dat
Line 40: Flat subfile is scaled in flat direction 1 16 11.5 12.75 15.336 1.33 -0.88 0.131 0 0.235 1.582 -0.89 -1.315 0.195 4-4ndis.dat
Contains some t-junctions as mentioned above.
The space in front of each linetype 1 to 5 should be removed.
Line 40: Flat subfile is scaled in flat direction 1 16 11.5 12.75 15.336 1.33 -0.88 0.131 0 0.235 1.582 -0.89 -1.315 0.195 4-4ndis.dat
Contains some t-junctions as mentioned above.
The space in front of each linetype 1 to 5 should be removed.
Fixed the non-planar issue, which (I believe) should also fix the "T"-junction issue.
Existing certification-votes were deleted.
Existing certification-votes were deleted.
Figured out the "T"-junction issue.
The keyword set numbers are not right.
This print is used in this fig, on a flat silver part:
https://www.bricklink.com/v2/catalog/catalogitem.page?M=sw0527a
Set 7877 and 9493 use a different design, on a LBG part
https://www.bricklink.com/v2/catalog/catalogitem.page?M=sw0217
This print is used in this fig, on a flat silver part:
https://www.bricklink.com/v2/catalog/catalogitem.page?M=sw0527a
Set 7877 and 9493 use a different design, on a LBG part
https://www.bricklink.com/v2/catalog/catalogitem.page?M=sw0217
2021-10-24 15:05:01
I compared this model to figures I own. I listed those sets I remember buying, which contained this figure.
But, having said that, I will say that I don't have perfect vision (I've got thick lenses on my eyeglasses), and since I don't have access to a spectrometer or other high-tech gizmo to perfectly identify the exact color codes, it's certainly possible I may be using a wrong color-code. ;-)
I'd ask for an Admin to make an Official Assessment as to the Correct Color-Code(s), if possible, please. Either that, or a consensus among reviewers.
But, having said that, I will say that I don't have perfect vision (I've got thick lenses on my eyeglasses), and since I don't have access to a spectrometer or other high-tech gizmo to perfectly identify the exact color codes, it's certainly possible I may be using a wrong color-code. ;-)
I'd ask for an Admin to make an Official Assessment as to the Correct Color-Code(s), if possible, please. Either that, or a consensus among reviewers.
[PTadmin]
edited the part header.
2022-11-01 14:35:01
I'm sorry, but my objection still stands.
Some of the set numbers, and now the added part reference numbers, refer to a different print.
Look at the colour of the eye. Lavender or Red?
And there is a Dark blue ribbon around the part. Not present on those reference parts.
The print in this file, is used in this fig, on a flat silver part:
https://www.bricklink.com/v2/catalog/catalogitem.page?M=sw0527a
So the print is of a R2-D2 head, but form another, later design.
Some of the set numbers, and now the added part reference numbers, refer to a different print.
Look at the colour of the eye. Lavender or Red?
And there is a Dark blue ribbon around the part. Not present on those reference parts.
The print in this file, is used in this fig, on a flat silver part:
https://www.bricklink.com/v2/catalog/catalogitem.page?M=sw0527a
So the print is of a R2-D2 head, but form another, later design.
Upon review, I agree with Magnus
Here's this part:
https://rebrickable.com/parts/30367cpr1000/brick-round-2-x-2-dome-top-with-lavender-dots-dark-blue-print-r2-d2/
And here's the part used in the keyword sets:
https://rebrickable.com/parts/30367cpr0006/brick-round-2-x-2-dome-top-with-blue-print-r2-d2/71/
I'll change the keywords.
Here's this part:
https://rebrickable.com/parts/30367cpr1000/brick-round-2-x-2-dome-top-with-lavender-dots-dark-blue-print-r2-d2/
And here's the part used in the keyword sets:
https://rebrickable.com/parts/30367cpr0006/brick-round-2-x-2-dome-top-with-blue-print-r2-d2/71/
I'll change the keywords.
[PTadmin]
edited the part header.
2022-11-01 17:45:01
2022-11-01 17:45:01
Keywords and Title changed to reflect the correct part.
2022-11-01 18:35:01
Thanks.
2022-11-02 20:10:02
Do you see any remaining problems with the sub-files?
If I run this file through Edger2 it detects T-junctions here, between the subfiles:
2 12 8.5981 .3462 3.5618 7.6434 .3462 4.9903
2 12 12.8871 2.4258 -5.3382 9.8635 2.4261 -9.8635
2 12 -12.8872 2.4259 5.3383 -9.8636 2.4262 9.8636
2 12 4.145 4.686 -15.6608 6.309 4.686 -15.23
Looks like all errors are in the ps0s04 subfile.
And some of the condlines in that subfile are wrong.
2 12 8.5981 .3462 3.5618 7.6434 .3462 4.9903
2 12 12.8871 2.4258 -5.3382 9.8635 2.4261 -9.8635
2 12 -12.8872 2.4259 5.3383 -9.8636 2.4262 9.8636
2 12 4.145 4.686 -15.6608 6.309 4.686 -15.23
Looks like all errors are in the ps0s04 subfile.
And some of the condlines in that subfile are wrong.
2023-09-09 14:12:51
2024-04-26 18:44:17
Keyword/color issue: 75092 has ITEM 6055159 (553pb017a on BrickLink). 6055159 has a reddish eye, not lavender
ACTION ITEM: 75092 should be removed from keywords
the other sets in the list use element 6150296 (553pb017b on BrickLink). 6150296 does have a lavender eye
ACTION ITEMS:
for this DAT file (lavender eye):
color 100 should be changed to color 325
color 232 should be changed to color 322
NOTES:
100 stopped being used in 1999 (and is reddish, not lavender colored)
232 stopped being used in 2007
I have a physical copy of the part, and an official LEGO palette
ACTION ITEM: 75092 should be removed from keywords
the other sets in the list use element 6150296 (553pb017b on BrickLink). 6150296 does have a lavender eye
ACTION ITEMS:
for this DAT file (lavender eye):
color 100 should be changed to color 325
color 232 should be changed to color 322
NOTES:
100 stopped being used in 1999 (and is reddish, not lavender colored)
232 stopped being used in 2007
I have a physical copy of the part, and an official LEGO palette
See Joshua's comments above
1) removed "set 75092" from keywords
2) replaced color-100 with color-325
3) replaced color-232 with color-322
2) replaced color-100 with color-325
3) replaced color-232 with color-322
Lavender is Ldraw Code 31. 325 is the LEGOID.
replaced color-325 with color-31...
2024-04-30 17:07:07
2024-05-02 20:58:26
2024-05-03 01:22:33
2024-05-28 02:57:15
Release 2024-04
Creative Commons Attribution License information
This part is copyright © Franklin W. Cain
Licensed under CC BY 4.0
Edits:
LDraw.org Parts Tracker,
Orion Pobursky,
3D View
Website copyright ©2003-2025 LDraw.org, see Legal Info for details.
LDraw is a completely unofficial, community run free CAD system which represents official parts produced by the LEGO company.
LDraw™ is a trademark owned and licensed by the Estate of James Jessiman
LEGO® is a registered trademark of the LEGO Group, which does not sponsor,
endorse, or authorize this site. Visit the official Lego website at
http://www.lego.com
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.