Vlad Neverov

>This was on the list of changes I intended to make for version 1.0. I want to increase the use of the function framework throughout raysect. The spectral functions and...

In addition to the fix suggested by @jacklovell, the figure can be initialised with the `self.name` assigned to the `num` argument (it accepts strings as well as the numbers). In...

> @vsnever could I make a request that new features are discussed via the issue tracker before implementation and merge request. Yes, I agree, I should have to open a...

> I was going to add a camera called LightProbe that performs even sampling over a sphere, with optional range restriction and with configurable mapping to a rectangle. I’ll try...

I updated the documentation for the API and demonstrations. Regarding the `__getstate__()` and `__setstate__()` methods, I think these are not necessary in the material class.

I ran into this issue a couple of weeks ago on the JET cluster, but didn't link it to a Cython change, unfortunately. I thought it was some kind of...

By the way, this affects not only the function framework, but the entire math framework: points, vectors, quaternions, affine matrices.

But `1 / s_incident.z` is not a constant. Also, there are two demos in demos/reflectivity that plot `RoughConductor` BSDFs by calling `bsdf()` method. I noticed that because I have some...

Thank you for your answer. The `bsdf()` method is not used in the sampling at all, it seems that it was added by @mattngc just for testing (see this #214)....

I think the implementation of the `next_intersection()` method is inconsistent with its intended behaviour. The description of this method says: https://github.com/raysect/source/blob/20f57259136ded2db692a967e486ebec88066b8a/raysect/core/scenegraph/primitive.pyx#L105-L119 Unlike any other primitive in Raysect, there are up...