Eh, that looks kinda boring. Try looking at it from a different angle or
use different primitive creation parameters.
On Thu, Mar 15, 2018 at 10:04 PM, Sreyansh Jain <sreyanshjai...@gmail.com>
wrote:
> Okay, I got your point. I've attached the performance stats for 2048x2048
> pixels as well as the rendering files for 512x512 pixels. While
> render_c.png gets saved automatically, the render_cl.png file is a
> screenshot.
>
> Warm Regards,
>
> *Sreyansh Kumhar Jain*
> 4th Year Undergraduate Student
> Department of Mechanical Engineering
> Indian Institute of Technology, Kharagpur
> *+91-9933958066 <+91%2099339%2058066>*
>
> sreyanshjai...@gmail.com
> Facebook <https://www.facebook.com/sreyansh.sonu> | LinkedIn
> <https://www.linkedin.com/in/sreyansh-kumhar-jain-a61428104/>
>
> On Thu, Mar 15, 2018 at 10:17 AM, Christopher Sean Morrison <
> brl...@mac.com> wrote:
>
>> You’re not specifying rt options correctly. Run “man rt” to read the
>> manual page on what each of the options means.
>>
>> The permission denied error is because you ran it previously or your
>> current working directory is a read-only location. The -z one isn’t
>> working, you just think it is. :)
>>
>> As it apparently wasn’t obvious, the “render_X.png" was just an example
>> to use for an output file name. You want something like render_c.png for
>> the C version and render_ocl.png for the OpenCL version. Really, you
>> probably want to specify an entire /path/to/some/folder/file.png in case
>> you are running from a read-only path (pwd to find out).
>>
>> Once you run rt -o some_file.png one time, the some_file.png file will be
>> write-protected so you don’t accidentally overwrite it. That means you’ll
>> need to delete it if you want to output that same file again or you’ll need
>> to use a different file name.
>>
>> Sean
>>
>>
>> On Mar 14, 2018, at 8:06 PM, Sreyansh Jain <sreyanshjai...@gmail.com>
>> wrote:
>>
>> When I use *rt -o render_X.png -s2048*, it is showing something like:-
>> Error: Can't open 'render_X.png' for reading/writing (permission denied).
>> But it is working when I use *rt -z render_X.png -s2048*.
>>
>> I'm unable to gauge why!
>>
>>
>>
>>
>>
>> Warm Regards,
>>
>> *Sreyansh Kumhar Jain*
>> 4th Year Undergraduate Student
>> Department of Mechanical Engineering
>> Indian Institute of Technology, Kharagpur
>> *+91-9933958066 <+91%2099339%2058066>*
>>
>> sreyanshjai...@gmail.com
>> Facebook <https://www.facebook.com/sreyansh.sonu> | LinkedIn
>> <https://www.linkedin.com/in/sreyansh-kumhar-jain-a61428104/>
>>
>> On Thu, Mar 15, 2018 at 4:03 AM, Christopher Sean Morrison <
>> brl...@mac.com> wrote:
>>
>>> Thank you! ... two questions. One, what do the renderings look like?
>>> Two, is the performance any better if you give it more work?
>>>
>>> Maybe compare: rt -o render_X.png -s2048
>>>
>>> Cheers!
>>> Sean
>>>
>>> On Mar 14, 2018, at 6:00 PM, Sreyansh Jain <sreyanshjai...@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>> I've attached the screenshots for your reference. I hope this is what
>>> you were looking for.
>>>
>>> Warm Regards,
>>>
>>> *Sreyansh Kumhar Jain*
>>> 4th Year Undergraduate Student
>>> Department of Mechanical Engineering
>>> Indian Institute of Technology, Kharagpur
>>> *+91-9933958066 <+91%2099339%2058066>*
>>>
>>> sreyanshjai...@gmail.com
>>> Facebook <https://www.facebook.com/sreyansh.sonu> | LinkedIn
>>> <https://www.linkedin.com/in/sreyansh-kumhar-jain-a61428104/>
>>>
>>> On Wed, Mar 14, 2018 at 12:44 PM, Christopher Sean Morrison <
>>> brl...@mac.com> wrote:
>>>
>>>> Screenshot? :)
>>>>
>>>> Ideally a comparison of superell from non-opencl next to the same
>>>> rendered via opencl…
>>>>
>>>> Cheers!
>>>> Sean
>>>>
>>>>
>>>> On Mar 13, 2018, at 5:48 PM, Sreyansh Jain <sreyanshjai...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I've submitted the patch file. Do let me know suggestions for that, if
>>>> any. I'll share the rough initial draft of the proposal for your review and
>>>> recommendation soon.
>>>>
>>>>
>>>> Warm Regards,
>>>>
>>>> *Sreyansh Kumhar Jain*
>>>> 4th Year Undergraduate Student
>>>> Department of Mechanical Engineering
>>>> Indian Institute of Technology, Kharagpur
>>>> *+91-9933958066 <+91%2099339%2058066>*
>>>>
>>>> sreyanshjai...@gmail.com
>>>> Facebook <https://www.facebook.com/sreyansh.sonu> | LinkedIn
>>>> <https://www.linkedin.com/in/sreyansh-kumhar-jain-a61428104/>
>>>>
>>>> On Tue, Mar 13, 2018 at 7:40 AM, Christopher Sean Morrison <
>>>> brl...@mac.com> wrote:
>>>>
>>>>> Sreyansh,
>>>>>
>>>>> Before moving onto other primitives, please submit a patch file with
>>>>> your changes (including any new files) and demonstrate the superell
>>>>> working
>>>>> via OpenCL…
>>>>>
>>>>> You should definitely be drafting a proposal for review at this
>>>>> point. Proposal submissions opened today.
>>>>>
>>>>> Cheers!
>>>>> Sean
>>>>>
>>>>>
>>>>> On Mar 12, 2018, at 5:50 PM, Sreyansh Jain <sreyanshjai...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Thank you so much for the detailed guidance. Having gone through all
>>>>> the reference codes given, I've successfully ported the SUPERELL primitive
>>>>> to OpenCL. I'll try to do the same for HYP and others as well before
>>>>> the final application deadline. Should I proceed with drafting the
>>>>> proposal for review or is there something else that needs to be done?
>>>>>
>>>>> Eagerly looking to your revert.
>>>>>
>>>>>
>>>>> Warm Regards,
>>>>>
>>>>> *Sreyansh Kumhar Jain*
>>>>> 4th Year Undergraduate Student
>>>>> Department of Mechanical Engineering
>>>>> Indian Institute of Technology, Kharagpur
>>>>> *+91-9933958066 <+91%2099339%2058066>*
>>>>>
>>>>> sreyanshjai...@gmail.com
>>>>> Facebook <https://www.facebook.com/sreyansh.sonu> | LinkedIn
>>>>> <https://www.linkedin.com/in/sreyansh-kumhar-jain-a61428104/>
>>>>>
>>>>> On Tue, Mar 6, 2018 at 10:56 PM, Vasco Alexandre da Silva Costa <
>>>>> vasco.co...@gmail.com> wrote:
>>>>>
>>>>>> Hello!
>>>>>> You can start by implementing one of the primitives which hasn't been
>>>>>> ported over to OpenCL yet.
>>>>>> There were a lot of issues with porting the HRT primitive last year,
>>>>>> probably because of the solver, so I would advise you to try to port
>>>>>> something simpler like either HYP or SUPERELL which shouldn't have any
>>>>>> issues.
>>>>>>
>>>>>> There is a quick reference guide to BRL-CAD MGED commands and
>>>>>> primitives here:
>>>>>> http://brlcad.org/w/images/5/52/MGED_Quick_Reference_Card.pdf
>>>>>>
>>>>>> Here is a reference card for OpenCL 1.2 (what we currently use)
>>>>>> commands and language constructs:
>>>>>> https://www.khronos.org/files/opencl-1-2-quick-reference-card.pdf
>>>>>>
>>>>>> I code for BRL-CAD using the Linux operating system. The other
>>>>>> developers typically use either that or Mac OS X.
>>>>>> Make sure to setup your development environment and install OpenCL on
>>>>>> your system. This program might be of help since it queries the installed
>>>>>> OpenCL versions to determine the supported version, etc:
>>>>>> https://github.com/simleb/clinfo
>>>>>>
>>>>>> You should provide a patch for that primitive (HYP or SUPERELL)
>>>>>> before GSoC officially starts. It shouldn't be too hard to do since you
>>>>>> can
>>>>>> use one of the other already ported primitives (like ELL) as a template.
>>>>>> You basically need to port the ray-primitive intersection (shot) code
>>>>>> from
>>>>>> C to OpenCL and to provide the glue code which packs and unpacks that
>>>>>> primitive from the C side to the OpenCL side.
>>>>>>
>>>>>>
>>>>>> I have a task list, of things to do, for the OpenCL ray tracer here:
>>>>>> http://brlcad.org/wiki/User:Vasco.costa
>>>>>>
>>>>>> You can use this as a basis to write your actual proposal. Of the
>>>>>> things in that todo list I would say that PIPE, DSP, BOT plate mode, and
>>>>>> BREPs are the most significant.
>>>>>>
>>>>>> Before you write the proposal and allocate time for the tasks you
>>>>>> should read the relevant code that you will have to port from ANSI C/C++
>>>>>> to
>>>>>> OpenCL to get an idea of the complexity of the tasks. Most of the
>>>>>> relevant
>>>>>> code is located in this code tree:
>>>>>> https://svn.code.sf.net/p/brlcad/code/brlcad/trunk/src/librt
>>>>>> /primitives/
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> On Tue, Mar 6, 2018 at 4:28 PM, Sreyansh Jain <
>>>>>> sreyanshjai...@gmail.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I'm new to the open source community but I'm well-versed with
>>>>>>> Python, C and CUDA while a beginner in OpenCL. I went through the
>>>>>>> project
>>>>>>> ideas list and I believe I can contribute to one on *GPGPU
>>>>>>> Raytracing*. Can you guide me on how to start contributing to these
>>>>>>> as of now. I hope I'm not that late.
>>>>>>>
>>>>>>>
>>>>>>> Warm Regards,
>>>>>>>
>>>>>>> Sreyansh Kumhar Jain
>>>>>>> 4th Year Undergraduate
>>>>>>> IIT Kharagpur
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------
>>>>>>> ------------------
>>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>>>>>> m.link/slashdot
>>>>>>> _______________________________________________
>>>>>>> BRL-CAD Developer mailing list
>>>>>>> brlcad-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Vasco Alexandre da Silva Costa
>>>>>> PhD in Computer Engineering (Computer Graphics)
>>>>>> Instituto Superior Técnico/University of Lisbon, Portugal
>>>>>>
>>>>>> ------------------------------------------------------------
>>>>>> ------------------
>>>>>> Check out the vibrant tech community on one of the world's most
>>>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>>>>> m.link/slashdot
>>>>>> _______________________________________________
>>>>>> BRL-CAD Developer mailing list
>>>>>> brlcad-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>>>>
>>>>>>
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>>>> m.link/slashdot_______________________________________________
>>>>> BRL-CAD Developer mailing list
>>>>> brlcad-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------
>>>>> ------------------
>>>>> Check out the vibrant tech community on one of the world's most
>>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>>>> m.link/slashdot
>>>>> _______________________________________________
>>>>> BRL-CAD Developer mailing list
>>>>> brlcad-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>>>
>>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>>> m.link/slashdot_______________________________________________
>>>> BRL-CAD Developer mailing list
>>>> brlcad-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>>> m.link/slashdot
>>>> _______________________________________________
>>>> BRL-CAD Developer mailing list
>>>> brlcad-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>>
>>>>
>>> <superell_c.png>
>>>
>>> <superell_cl.png>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>>> m.link/slashdot
>>>
>>> _______________________________________________
>>> BRL-CAD Developer mailing list
>>> brlcad-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> BRL-CAD Developer mailing list
>>> brlcad-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>>
>>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sd
>> m.link/slashdot_______________________________________________
>> BRL-CAD Developer mailing list
>> brlcad-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> BRL-CAD Developer mailing list
>> brlcad-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>>
>>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> BRL-CAD Developer mailing list
> brlcad-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/brlcad-devel
>
>
--
Vasco Alexandre da Silva Costa
PhD in Computer Engineering (Computer Graphics)
Instituto Superior Técnico/University of Lisbon, Portugal
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
