Hello Sean,
I wonder if I should continue working on rtweight now, or if the report can
be written with the code in the current state.
If so, we would need to discuss what changes should come next, and how.
Thanks,
Mario.
On 15 October 2017 at 19:58, Mario Meissner <mr.rash@gmail.com>
n solid effort.
>
> I talked with Adam yesterday and gave him an update and ETA on the report.
>
> Cheers!
> Sean
>
> On Oct 13, 2017, at 11:42 AM, Mario Meissner <mr.rash@gmail.com>
> wrote:
>
> Hello again!
>
> Attached code is cleaner and more t
, Mario Meissner <mr.rash@gmail.com> wrote:
> Hello everyone.
>
> I received an email from the SOCIS organizer saying that the coding period
> is finishing really soon. However I haven't received any news from your
> side. What is gonna happen now? Can we (and will we
basis. This
week I will integrate my code into rtweight.
Mario
On Oct 9, 2017 11:05, "Mario Meissner" <mr.rash@gmail.com> wrote:
> Hi people!
>
> I proudly present my latest work, attached here. It features a clean
> algorithm to compute the average density of
, feedback welcome.
Thank you,
Mario.
On 6 October 2017 at 19:41, Mario Meissner <mr.rash@gmail.com> wrote:
> Hi Daniel,
> thank you! In the end the problem was that I didn't run cmake after svn
> up.
>
> Attached goes today's work. I coded the function 'reg
, Mario Meissner <mr.rash@gmail.com> wrote:
> So I ended up designing a new algorithm and would love to get some
> feedback before I implement it.
> Here it goes:
>
> * Sort the points from 'left to right' (distance of projection to inhit)
> * Look for the closest
it.
This algorithm would be the last piece of the puzzle to finish off the
project.
Mario.
On Oct 1, 2017 16:23, "Mario Meissner" <mr.rash@gmail.com> wrote:
Hi!
I forgot to mention it before leaving. I went on a spontaneous trip to
Prage for a few days. I will be back w
Hi!
I forgot to mention it before leaving. I went on a spontaneous trip to
Prage for a few days. I will be back with more updates on monday.
Mario.
On 25 September 2017 at 13:13, Mario Meissner <mr.rash@gmail.com> wrote:
> Attached goes new code with the changes I mentioned. On
.
I have yet to come up with a more elegant way of checking which 'tiles' our
segment will cross and which not.
Back with more tomorrow.
Mario.
On 23 September 2017 at 20:20, Mario Meissner <mr.rash@gmail.com> wrote:
> Hello everyone.
>
> I wrote this on my log a few hours ag
it all more readable, and most importantly, will
support more situations than before, removing several flaws.
Mario.
On 23 September 2017 at 18:01, Mario Meissner <mr.rash@gmail.com> wrote:
> I'm passing two arguments to my segment_density, which are inhit and
>> outhit points.
&
>
> I'm passing two arguments to my segment_density, which are inhit and
> outhit points.
> I now realize that these are pointers and could change unexpectedly within
> the call if we run multiple threads.
> How can I make this safe? Should I BU_GET safe heap memory to store the
> points for the
>
> What I meant was: Why has your intersection_t struct an intersect member?
> You don't use it.
> I wanted to use it as a surrogate for your NULL return value but what was
> your reason?
>
I just didn't really know what that intersect member was in your example.
So I just set it to 0 in the
the
points for the call, or pass the coordinates one by one as actual numbers?
On 22 September 2017 at 17:07, Mario Meissner <mr.rash@gmail.com> wrote:
> Hello!
>
> Mass being 0 all the time was because the reg_los of my region was 0 for
> whatever reason. Hard-coding a reg_lo
Hello!
Mass being 0 all the time was because the reg_los of my region was 0 for
whatever reason. Hard-coding a reg_los of 100 (and thus a 'factor' of 1)
works and I now get a mass value (however unfortunately not the value I
expect, yet). Attached goes code. Any hints on why the reg->reg_los
heap and don't use its
> intersect flag. But what is really bad is that you don't free it if it
> won't be used any more.
>
> BTW, do you have a Chinese OS version? Your diff files contain Chinese
> comments.
>
>
> Regards,
> Daniel
>
>
> 2017-09-21
Hi Daniel.
Thank you for your response. Negative values may have been only due to
using the wrong formatting tag while printing values. I have cleaned up
some unused variables and fixed the intersection by using your suggestion.
Mass is 0 in the total_weight variable, as if the code wasn't
need some help regarding the negative values
issue, at least once I'm sure the two points above aren't the cause.
Mario.
On 17 September 2017 at 21:16, Mario Meissner <mr.rash@gmail.com> wrote:
> After my linux build decided to not compile anymore (and haven't been able
> to fix
://puu.sh/xAmiE/b5fa0dfab8.png
Mario.
On 8 September 2017 at 21:04, Mario Meissner <mr.rash@gmail.com> wrote:
> Peopleee!
>
> Here goes today's work. I'm proud to announce the example I modeled a few
> days ago now works correctly!!
> Code still contains my debug prin
looking for flaws by setting up other examples, and
while doing so I should also clean it up a bit since the code grew over 600
lines now, quite difficult to read and understand.
Screenshot:
https://puu.sh/xuIXk/9626ce2fb6.png
Mario.
On 8 September 2017 at 19:56, Mario Meissner <mr.r
Hi Daniel!
Thank you a lot for your reply. I was focused on generating the bisector to
intersect two lines, but intersecting the actual plane is much simpler. I
made a little function to intersect a plane with a line (partially taken
from this stackoverflow post
I forgot to reply to this yesterday.
r70209 fixed all my problems.
Build successful on all platforms (with mingw still installed).
Thank you a lot!
Mario.
On 6 September 2017 at 13:18, Clifford Yapp <cliffy...@gmail.com> wrote:
> On Wed, Sep 6, 2017 at 5:58 AM, Mario Meissner
find anything that could help me. Do
you know any macro that could be useful here?
Otherwise I will need to make some of my own for this! If so, any ideas on
how to approach it?
Mario.
On 6 September 2017 at 18:39, Mario Meissner <mr.rash@gmail.com> wrote:
> After considerin
them for the boundary calculation phase, replacing my current equation. We
can think about it later.
I will start working on this unless you think there is a superior approach
to this.
Mario.
On 6 September 2017 at 17:33, Mario Meissner <mr.rash@gmail.com> wrote:
> Hey Se
not determine linker language for target: png
CMake Error: CMake can not determine linker language for target: png_static
Interestingly enough on the Ubuntu subsystem it works just fine.
Mario.
On Sep 4, 2017 5:13 PM, "Mario Meissner" <mr.rash@gmail.com> wrote:
> Interesting.
>
> Interesting. May I ask in which area of Germany?
>
In München!
Interesting. That looks like it is trying to execute the awk script
> in libpng's build, but that shouldn't happen on Windows normally...
> Do you have some Windows version of awk installed?
So apparently I do.
Hello everyone.
As you may have seen in my previous emails, I moved to Germany on the 1st
of this month. I am finally settled in my new place and am now setting up
my working environment on my laptop.
I am facing an issue with Visual Studio when I try to build the solution.
For now, and since my
, 2017 09:58, "Christopher Sean Morrison" <brl...@mac.com> wrote:
>
> On Aug 30, 2017, at 6:38 AM, Mario Meissner <mr.rash@gmail.com> wrote:
>
> Implemented the mentioned changes and fixed projections not being skipped
> correctly when they shoul
for this case.
More thorough tests with non-mid-point boundaries will follow.
Mario.
On 29 August 2017 at 18:05, Mario Meissner <mr.rash@gmail.com> wrote:
> Made a mistake in the last line, should be:
> PR1B = (- DP1PR1^2 + DP2PR2^2 + PR2PR1^2) / (2 * PR2PR1)
>
> Sorry
gt;
> I think it's easier this way (it's a quite simple O(1) operation) than to
> compute the actual mesh and then evaluate against it. It probably would me
> more elegant and maybe more efficient but it seems much more complex to me.
>
> Let me know what you think, I'll start workin
start working on it.
Mario.
On 29 August 2017 at 15:44, Mario Meissner <mr.rash@gmail.com> wrote:
> Hi Sean!
> Back from my trip now.
>
> The reason why I worked on projections is because you told me to do so:
>
> Not the distance between points, but distance to the
n <brl...@mac.com>
wrote:
>
> > On Aug 17, 2017, at 6:28 AM, Mario Meissner <mr.rash@gmail.com>
> wrote:
> >
> > So I think now that n-points are working for convex regions, I think the
> next steps would be:
> > • Integrate vectors into exi
year abroad. I hope to be able to set myself up there
quickly to continue working on this.
Cheers!
Mario.
On 18 August 2017 at 21:44, Mario Meissner <mr.rash@gmail.com> wrote:
> I found a flaw in my current code.
> I considered all points to be valid and projected them
Mario Meissner <mr.rash@gmail.com>:
> Sean,
> So I've given the transition concept a deep thought and I think I may have
> found one way it could work.
> We define a transition object that links to two points and has a float
> value stored. This value indicates the r
available? I tried looking for it but didn't find anything.
I hope you'll find some time to discuss this soon.
Mario.
2017-08-18 17:40 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hello everyone.
> Quick question regarding bu_lists.
>
> When I BU_LIST_PUSH to th
the elements in the order I pushed them.
Do I need to use APPEND and keep a pointer to my last added element to get
the behaviour I need? Why?
Mario.
2017-08-18 13:38 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Good morning / afternoon !
>
> I've started considerin
into the mud.
Mario.
2017-08-17 12:28 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> So I think now that n-points are working for convex regions, I think the
> next steps would be:
>
>- Integrate vectors into existing point system.
> - Let the user input vectors
point of my
proposed steps.
Attached goes code with minor cleanup changes over yesterday. If possible,
use this for review.
Happy coding!
Mario.
2017-08-15 22:28 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Sean!
> Implemented the math and did some bug hunting. I successfully ran
feedback now, hope you'll have some time to review
this.
https://puu.sh/xaUwS/c2f30fc275.png
Mario.
2017-08-14 19:44 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> The sorting function is now correctly implemented and works as expected
> with projection structs, sorting them by dista
Hello Sean.
Things got a bit messy on the previous thread, I apologize for that.
I somehow managed to send emails only to myself for the last three days.
I decided to start a new fresh thread and include the text of the last
three emails here, as well as the newest code I have. It is a new
is not yet working. I send it anyways in the
hopes of receiving much appreciated feedback.
2017-08-11 23:28 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Sean,
>
> I’ve started working on Voronoi model for non-continuous density
> evaluation using points. For now only 0
:26 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
>
> -- Forwarded message --
> From: MarioPC <mr.rash@gmail.com>
> Date: 2017-08-10 20:33 GMT+02:00
> Subject: RE: [brlcad-devel] Example of heterogeneous density +
> masscalculation
> To: Mari
-- Forwarded message --
From: MarioPC <mr.rash@gmail.com>
Date: 2017-08-10 20:33 GMT+02:00
Subject: RE: [brlcad-devel] Example of heterogeneous density +
masscalculation
To: Mario Meissner <mr.rash@gmail.com>
Okay,
So since stuff doesn’t seem to wo
My last two emails (of today and yesterday) got accidentally sent only to
myself (I probably pressed reply to an email from myself and it somehow
didn't get sent to the mailing list). I will now re-send them to the
mailing list.
Sorry for this.
Mario.
2017-08-09 23:04 GMT+02:00 Mario Meissner
Hi Sean!
Thank you a lot for the details. The visualization of Voronoi points was
really helpful. I think I understand your vision and will work on
implementing the first steps as soon as the stuff I mention below is done.
I'm running into some trouble with my code. I need to call
Hey Sean!
Glad to hear back from you! Hope your trip went fine.
Tons of new information! Let me try to dig through it.
Both this prior version and the latest viewweight.c suffer from the comment
> I originally made, namely that the 0 and 1 point cases are not what i would
> call “complete".
I would also like to get some more info about how you mentioned we could
model those complex examples I sent. You said something about
half-spaces...How would it work exactly?
2017-08-07 14:47 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hi again!
>
> A few questions:
>
ean distance between the points? (as in, point
b is closer to point B than it is to point A, so it gets more influence
from it's vector). I'm attaching the example we talked about here again for
your convenience.
Mario.
2017-08-06 10:10 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
>
, the code itself, and the box I used.
Output: https://puu.sh/x2n0W/406b7a0bb9.png
Have a nice weekend!
Mario.
2017-08-04 22:36 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
>
> Is there a new version of the code demonstrating them working?
>
>
> Yes, it is attached to tod
Is there a new version of the code demonstrating them working?
Yes, it is attached to today's email. It should compile and produce an
rtexample binary that runs the example I set up correctly.
There are a variety of cases with 2points that should also be explored and
ensure are being handled
.
Stay safe!
Mario.
2017-08-03 17:33 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hi!
> I also now added a curve to the blade by intersecting it with a stretched
> out sphere. I considered various options but this one ended up being my
> favorite.
> Am not sure why the res
make vectors from all points to the first one.
Will try to make a simple 4 point (origin and the three axis directions)
example work.
Mario.
2017-07-31 19:12 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hello Sean!
>
> As you suggested, I reverted some of the changes I mad
Surprisingly, svn update solved the issue.
My bad for not running the latest sources.
Thank you!
2017-07-28 15:24 GMT+02:00 Christopher Sean Morrison <brl...@mac.com>:
>
> > On Jul 28, 2017, at 4:22 AM, Mario Meissner <mr.rash@gmail.com>
> wrote:
> >
> >
to make a new vector just to
make the macro work.
Mario.
2017-07-30 17:40 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> After it’s working, that’s the next logical step. Don’t want to
>> scope-creep the complexity prematurely, but we will eventually want
>> mate
>
> After it’s working, that’s the next logical step. Don’t want to
> scope-creep the complexity prematurely, but we will eventually want
> material objects defining the density (and other) material characteristics
> of an object (as a replacement for .density files and _DENSITY objects).
>
>
> I think you’re right on track. Your stubs in the code ( *_FACTOR and
> MAT_DENSITY) naturally lend themselves to substitution with a function, and
> implementing those functions figuring that out from your density_point
> structure next would be a good progression. I’d suggest starting with
Hi again.
I fixed the issues I mentioned and the snippet now works as intended. Just
compile and run rtexample to check it out.
I'll continue with the next snipped I proposed unless you think I should do
something else instead :P
Mario.
2017-07-27 22:42 GMT+02:00 Mario Meissner <mr.r
Hello everyone.
I'm facing an issue while trying to compile the whole solution in visual
studio.
There seem to be syntax errors inside winnt.h, a file I have never touched.
These errors showed up since I first tried to compile with VS weeks ago,
but never bothered me because they didn't
>
> This is great, please keep sharing. This looks potentially like the
> beginnings for what a proper material object (see TODO) might end up
> requiring/using for the typein interface.
>
Which TODO do you mean?
> Some feedback, you should use bu_fgets for portability. You're also also
> not
Hi Sean!
It's an extension that can be made after vectors are working. Basically
> instead of treating them as vectors, you'll need to treat the as half space
> plane definition. Calculating the density at any point will be the
> contribution of any given set of points, and knowing which ones
Christopher Sean Morrison <brl...@mac.com>:
>
>
> On Jul 26, 2017, at 10:59 AM, Mario Meissner <mr.rash@gmail.com>
> wrote:
>
> Sean,
>
> Today I started modifying rtexample.c so that it simulates a ray crossing
> several regions (tried with the goblet e
Sean,
Today I started modifying rtexample.c so that it simulates a ray crossing
several regions (tried with the goblet example) and returning the mass it
saw as it crossed each region. I assumed most stuff with predefined
constant values for now.
Most changes happened at lines 115 and 179.
Next
> This is flawed for one simple reason — material properties do not
> multiply. At least, not for any common materials I can think of that we
> care about.
>
The problem lies in the definition I gave to the vectors. I tried to use
them like follows:
If we have a vector that goes to the right
will try to make sense of
the existing code in the meantime.
Mario.
2017-07-19 13:40 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> As promised, a patch (literally) for yesterdays document. Instead of the
> sum used and explained in my last email I found it more convenient (a
or the half way diagonal example I mentioned above). Instead of just
summing one on top of the other, we have to make the operations step by
step and use the result of the first step as input for the second step.
I'll send a fix in one hour for yesterdays document so that it actually
does wha
We probably have some different ideas on how it should work, because of
your "the largest value should be 3*V=9". I thought that if we have a
horizontal vector going right, and a vertical vector going down, and we
take the diagonal that goes the full distance down and right (so basically
a 2D
to
the Distal Taper.
Mario.
2017-07-18 10:31 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Sean,
> thank you for the extensive explanation, and sorry for the
> misunderstanding. When you said that "instead of considering the ray line
> lets consider segments" I thou
ctions. Density at a specific
point could be retrieved by combining vectors and the rate of change
between two arbitrary points can be obtained through the vectors as well.
Will send new blade soon.
Mario.
2017-07-17 23:35 GMT+02:00 Christopher Sean Morrison <brl...@mac.com>:
>
, "Christopher Sean Morrison" <brl...@mac.com>
escribió:
>
> On Jul 17, 2017, at 2:42 PM, Mario Meissner <mr.rash@gmail.com> wrote:
>
> It took me way longer than it should have and I don't know how to round up
> the edges but here goes an initial ro
It took me way longer than it should have and I don't know how to round up
the edges but here goes an initial rough model of the blade using two arb6
primitives.
2017-07-17 16:37 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hello Sean.
>
> In the general case, we do not n
Hello Sean.
In the general case, we do not necessarily know the “shape" of the
> geometry, particularly having an equation for the geometry to substitute in
> a line equation like in your case. For example, the sword blade case might
> be constructed as a union of several objects, like if you
Hi Sean.
- You are right, given the endless possibilities of a function like
this, it may not be obvious to define the function in the file as I
mentioned. Some re-considerations would need to be made in order to support
any number of arguments, any polynomial degree. Who knows,
what you
mentioned.
Mario.
2017-07-14 9:03 GMT+02:00 Christopher Sean Morrison <brl...@mac.com>:
>
> On Jul 13, 2017, at 10:45 AM, Mario Meissner <mr.rash@gmail.com>
> wrote:
> [snip]
> However, as I do not yet understand how rtweight currently behaves, I do
> no
Hello.
I have calculated the mass of an example of an heterogeneous object using a
function that defines the density of an object in each point in space, and
integration to obtain it's mass.
You can see it here:
https://drive.google.com/file/d/0Bz6hfFobLeoyZC1vQ1JwSU05NDg/view
I believe that
Hello everyone.
I wanted to ask if anyone knows what happened with Christopher Sean? He is
my mentor for SOCIS but I didn't get a reply from him for weeks now. Is he
on vacation, or did something happen to him?
Cheers,
Mario.
Ah, after going into Visual Studio and building the install target, the
binaries showed up. Thank you!
2017-06-22 8:28 GMT+02:00 Daniel Roßberg :
> > Following the compilation instructions, the built filesystem on linux
> > doesn't yield any Release folder, just a bin
I don't know if this helps but running rt separately works flawlessly.
2017-06-21 19:27 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hi Daniel.
> Following the compilation instructions, the built filesystem on linux
> doesn't yield any Release folder, just a bin fold
Hi Daniel.
Following the compilation instructions, the built filesystem on linux
doesn't yield any Release folder, just a bin folder. That folder contains
dozens of executables, including mged and archer. However if you look at
the screenshots I attached, you can see that on windows I do get a
Hello!
I'm working my way through the introductory guide, and I haven't been able
to use raytracing. As I try to do as the guide tells me to, this error
shows up: http://imgur.com/a/RGCBV , but only after a few minutes of
waiting. I'm using Arch Linux (Antergos) x64. Am I missing a library? I had
ative.
Regards,
Daniel
2017-06-19 12:50 GMT+02:00 Mario Meissner <mr.rash@gmail.com>:
> Hello everyone.
> I'm Mario Meissner, I have been elected to work for BRLCAD during the
> summer, in case SOCIS happens. Apparently, they are having administrative
> issues and the s
Hello everyone.
I'm Mario Meissner, I have been elected to work for BRLCAD during the
summer, in case SOCIS happens. Apparently, they are having administrative
issues and the start of the coding period has been delayed. Anyway I
decided to at least set myself up and start on my own.
I'm trying
Hello everyone!
My name is Mario and I'm a Spanish university student.
I am really interested in applying to the SOCIS program, especially for the
Density Functions project.
As soon as I have the available time (finals incoming!) I will try to build
the source code and have a look at it.
Are
81 matches
Mail list logo