 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have extracted some of the data fields from the Yale Bright Star
Catalogue and converted them to SDL. This catalog contains all
nighttime stars of magnitude 6.5 and brighter (roughly all nighttime
stars visible to the naked eye), plus a few dimmer ones. The
BrightStar5 module includes more data fields than the include file
Rarius published a while back, including catalog designations and color
data. Macros are included for star coloration and Bayer designation
labels. You can also seek individual stars by Bayer, Draper, Flamsteed,
or SAO designations.
Rarius stated that the catalog is in the public domain. I could not
determine the intellectual property status from the published sources,
and in the process of trying to find out, I ended up having a very nice
phone conversation with one of the authors, Dr. Warren!
The 5th edition of the catalog, as it stands, is in a preliminary state.
(The primary author died in 2007.) There is no projected date for
final publication.
POV-Ray 3.7.1 beta 2 will crash hard with this module. Think Bayer
designations, and if you've been following p.beta-test, you'll know
exactly why it crashes. Some of the 3.7.1 alphas (including some 2015
vintages) also crashed, but 3.7.0 works fine. The latest master passes,
so everything should be fine when beta 3 is released.
http://lib.povray.org/searchcollection/index2.php?objectName=BrightStar5&contributorTag=Cousin%20Ricky
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky wrote on 08/02/2017 14:08:
> I have extracted some of the data fields from the Yale Bright Star
> Catalogue and converted them to SDL. This catalog contains all
> nighttime stars of magnitude 6.5 and brighter (roughly all nighttime
> stars visible to the naked eye), plus a few dimmer ones. The
> BrightStar5 module includes more data fields than the include file
> Rarius published a while back, including catalog designations and color
> data. Macros are included for star coloration and Bayer designation
> labels. You can also seek individual stars by Bayer, Draper, Flamsteed,
> or SAO designations.
>
> Rarius stated that the catalog is in the public domain. I could not
> determine the intellectual property status from the published sources,
> and in the process of trying to find out, I ended up having a very nice
> phone conversation with one of the authors, Dr. Warren!
>
> The 5th edition of the catalog, as it stands, is in a preliminary state.
> (The primary author died in 2007.) There is no projected date for
> final publication.
>
> POV-Ray 3.7.1 beta 2 will crash hard with this module. Think Bayer
> designations, and if you've been following p.beta-test, you'll know
> exactly why it crashes. Some of the 3.7.1 alphas (including some 2015
> vintages) also crashed, but 3.7.0 works fine. The latest master passes,
> so everything should be fine when beta 3 is released.
>
>
http://lib.povray.org/searchcollection/index2.php?objectName=BrightStar5&contributorTag=Cousin%20Ricky
>
It seems very interesting.
I hope to see soon some examples,
Paolo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Cousin Ricky <ric### [at] yahoo com> wrote:
> I have extracted some of the data fields from the Yale Bright Star
> Catalogue and converted them to SDL.
Thanks Richard! Great way to use the data. All of it impressive work.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-02-08 09:08 AM (-4), Cousin Ricky wrote:
> POV-Ray 3.7.1 beta 2 will crash hard with this module. Think Bayer
> designations, and if you've been following p.beta-test, you'll know
> exactly why it crashes. Some of the 3.7.1 alphas (including some 2015
> vintages) also crashed, but 3.7.0 works fine. The latest master passes,
> so everything should be fine when beta 3 is released.
POV-Ray 3.7.1 beta 3 works fine with this module.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-02-08 08:08 AM (-5), Cousin Ricky wrote:
> I have extracted some of the data fields from the Yale Bright Star
> Catalogue and converted them to SDL. [snip]
>
>
http://lib.povray.org/searchcollection/index2.php?objectName=BrightStar5&contributorTag=Cousin%20Ricky
I have uploaded BrightStar5 version 1.1, which has indexes on the data
arrays. The seek macros run *much* faster now.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/8/2017 8:08 AM, Cousin Ricky wrote:
> I have extracted some of the data fields from the Yale Bright Star
> Catalogue and converted them to SDL. This catalog contains all
> nighttime stars of magnitude 6.5 and brighter (roughly all nighttime
> stars visible to the naked eye), plus a few dimmer ones. The
> BrightStar5 module includes more data fields than the include file
> Rarius published a while back, including catalog designations and color
> data. Macros are included for star coloration and Bayer designation
> labels. You can also seek individual stars by Bayer, Draper, Flamsteed,
> or SAO designations.
>
> Rarius stated that the catalog is in the public domain. I could not
> determine the intellectual property status from the published sources,
> and in the process of trying to find out, I ended up having a very nice
> phone conversation with one of the authors, Dr. Warren!
>
> The 5th edition of the catalog, as it stands, is in a preliminary state.
> (The primary author died in 2007.) There is no projected date for
> final publication.
>
> POV-Ray 3.7.1 beta 2 will crash hard with this module. Think Bayer
> designations, and if you've been following p.beta-test, you'll know
> exactly why it crashes. Some of the 3.7.1 alphas (including some 2015
> vintages) also crashed, but 3.7.0 works fine. The latest master passes,
> so everything should be fine when beta 3 is released.
>
>
http://lib.povray.org/searchcollection/index2.php?objectName=BrightStar5&contributorTag=Cousin%20Ricky
>
The fuzzy circles don't look so great. I don't know if anything can be
done to improve them however. In video games, stars are often reduced to
1 pixel. But I don't think in POVray there's an easy way to make a star
exactly 1 pixel big. Maybe with some trigonometry?
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Horvath <mik### [at] gmailcom> wrote:
But I don't think in POVray there's an easy way to make a star
> exactly 1 pixel big. Maybe with some trigonometry?
I worked that out obtain a constant-apparent-width cylinder for a bounding box,
and a Dupin cyclide for orbital trajectories.
Obtaining a constant 1-pixel width is pretty trivial with the orthographic
camera, since with the default camera, IIRC, 1 POV-unit = 1 pixel.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 10/02/2018 à 04:23, Bald Eagle a écrit :
> Mike Horvath <mik### [at] gmailcom> wrote:
> But I don't think in POVray there's an easy way to make a star
>> exactly 1 pixel big. Maybe with some trigonometry?
>
> I worked that out obtain a constant-apparent-width cylinder for a bounding box,
> and a Dupin cyclide for orbital trajectories.
> Obtaining a constant 1-pixel width is pretty trivial with the orthographic
> camera, since with the default camera, IIRC, 1 POV-unit = 1 pixel.
not really.
Unless your default camera is
...
up image_height*y
right image_width*x
...
but that's not the camera you get from
camera{ orthographic }
|| up: 0.000, 1.000, 0.000
|| right: 1.330, 0.000, 0.000
|| location: 0.000, 0.000, 0.000
|| direction: 0.000, 0.000, 1.000
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <jgr### [at] freefr> wrote:
> not really.
> Unless your default camera is
> ...
> up image_height*y
> right image_width*x
> ...
> but that's not the camera you get from
>
> camera{ orthographic }
>
> || up: 0.000, 1.000, 0.000
> || right: 1.330, 0.000, 0.000
> || location: 0.000, 0.000, 0.000
> || direction: 0.000, 0.000, 1.000
Well, then I guess I didn't remember correctly ;)
I vaguely recalled this discussion:
http://news.povray.org/povray.advanced-users/thread/%3Cweb.5845a06cc97737fcc437ac910%40news.povray.org%3E/
So modifying that so Pixel "size" is described in POV-units, then we could have
#macro Zoom (PixelSize)
camera {
orthographic
location <0, 0, -PixelSize>
look_at <0, 0, 0>
right (x*image_width )*PixelSize
up (y*image_height)*PixelSize
}
#end
(I haven't entirely determined what the best camera-to-lookAt distance is to
avoid some weird things happening)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I kinda wish there were a POV-Ray object that would be guaranteed to
always be 1 pixel big.
Mike
On 2/10/2018 5:14 PM, Bald Eagle wrote:
> Le_Forgeron <jgr### [at] freefr> wrote:
>
>> not really.
>> Unless your default camera is
>> ...
>> up image_height*y
>> right image_width*x
>> ...
>> but that's not the camera you get from
>>
>> camera{ orthographic }
>>
>> || up: 0.000, 1.000, 0.000
>> || right: 1.330, 0.000, 0.000
>> || location: 0.000, 0.000, 0.000
>> || direction: 0.000, 0.000, 1.000
>
> Well, then I guess I didn't remember correctly ;)
>
> I vaguely recalled this discussion:
>
http://news.povray.org/povray.advanced-users/thread/%3Cweb.5845a06cc97737fcc437ac910%40news.povray.org%3E/
>
> So modifying that so Pixel "size" is described in POV-units, then we could have
>
> #macro Zoom (PixelSize)
> camera {
> orthographic
> location <0, 0, -PixelSize>
> look_at <0, 0, 0>
> right (x*image_width )*PixelSize
> up (y*image_height)*PixelSize
> }
> #end
>
>
> (I haven't entirely determined what the best camera-to-lookAt distance is to
> avoid some weird things happening)
>
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
