-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
Added basic examples in how-to #24
Comments
@taoning A simple example of rpict is here: https://gist.github.com/sariths/4c93a1a87457edba112212a3e1b23c6a Let me know what you think. |
Looks good. Instead of If the sky In terms of sampling parameters, we can do
Is this similar to what you have in mind? |
Okay to all the suggestions. Any thoughts about ra_tiff, ra_bmp etc? I had
a comment towards the end of the gist.
…On Fri, Aug 4, 2023, 6:43 PM taoning ***@***.***> wrote:
Looks good. Instead of write_to_file, maybe just write? I think we have
file_path as the first argument, followed by data?
If the sky source is used for an octree, we can just feed the bytes to
stdin in oconv rather than write to a file first.
In terms of sampling parameters, we can do
params = SamplingParamters()
params.update_from_dict({"-ab":1})params.ad = 256
params.lw = 1 / params.ad
rpict(..., params=params.args())
Is this similar to what you have in mind?
—
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPBX6CAEZI6EMGTLBB5PD3XTWQK5ANCNFSM6AAAAAA3ESG46E>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sure, we can add those tools. |
Add examples for rtrace, rpict and rfluxmtx.
@taoning I added a discussion regarding the choice of input files here: #23
The text was updated successfully, but these errors were encountered: