Yeh, axis was the wrong term. I was thinking degrees of freedom.
However, I misunderstood the concept.
The extra dimensions are basically optical manipulation, like the other comment says with the red and blue lenses.
I thought it was more about the crystals attitude. So in addition to x, y and z, you also have alpha, beta, gamma.
Which would be 3 dimensions/axis with 6 degrees of freedom
Seems more like 5 axis than 5 dimensions.
Sounds like a slice through the crystal that can be moved up and down and rotated through 2 angles (eg roll and pitch)
That's like any FPS game ripping off any other FPS game.
Fight, capture, tame, train, breed animals.
Base building, research tree, enemy raids.
Exploration, resource gathering, survival.
I don't think Nintendo has a monopoly on enslaving animals.
I know what you mean, tho. It's always described as "Pokémon with guns and 3xE gameplay".
But does Nintendo actually have a case that will hold up in courts?
Pocketpair seems confident they can defend against it. So either they have done their research and are up for a fight. Or they (think they) are calling Nintendo's bluff.
But Nintendo has a whole pack of lawyers.
Unfortunately there are no details on what the patents being infringemed upon are, just that they relate to "Pocket Monster".
You can set a static IP on the router, disable it's DHCP, and have pihole manage DHCP with the routers static IP as the gateway
The financial insensitive to ensure only paying users can access the content offsets the cost of the different infrastructure.
YouTube needs to make money as cheaply as possible. They can't afford the processing to guarantee ad delivery and secure content like that.
If the infrastructure/delivery cost of securing content goes up, streaming services can raise their prices.
YT can't really serve more ads. The platform is already pretty packed with ads
Like I said, impressive work.
Converting science to shaders is an art.
I guess your coding standards follows scientific standards.
And I guess it depends on your audience.
I guess the perspective is that science/maths formulae are meant to be manipulated. So writing out descriptive names is only done at the most basic levels of understanding. Most of the workings are done on paper/boards, or manually. Extra letters are not efficient.
Whereas programming is meant to be understood and adapted. So self-describing code is key! Most workings are done within an IDE with autocomplete. Extra letters don't matter.
If you are targeting the science community with this, a paragraph about adapting science to programming will be important.
Scientists will find your article and go "well yeh, that's K2". But explaining why these aren't named as such will hopefully help them to produce useful code in the future.
The fun of code that spans disciplines!
Edit;
Om a side note, I am terrible at coding standards when I'm working with a new paradigm.
First is "make it work", after which it's pretty much done.
Never mind consistent naming conventions and all that.
The fact you wrote up an article on it is amazing!
Good work!
I presume the investigation is taking official testimonies and gathering actual (and traceable) evidence in order to legally confirm what we all know.
It's all amendment rights until it's one of the racist fucks that gets murdered.
Then the police get military equipment to deal with the rising crime rates.
Interesting.
I love creative applications of shaders. They are very powerful.
In my opinion only, but willing to discuss.
And I'll preface this by saying if I tried to publish a scientific paper and my formulas used a bunch of made up symbols that are not standardised, I imagine it would get a lot of corrections on peer review.
So, from a programming perspective, don't use abbreviations.
Basically working on naming.
I can read that TAU is the diffusion rate due to a comment. Then I dig further into the code as I am trying to figure something out and I encounter tau. Now I have to remember that tau is explained by a comment, instead of the name of the variable. Why not call it diffusionRate then have a comment indicating this is TAU.
A science person will be able to find the comment indicating where it is initialised and be able to adjust it without having to know programming. A programming person will be able to understand what it does without having to know science things.
Programming is essentially writing code to be read.
It's written once and read many times.
Similar with the K variables.
K is reactionRate.
K1 is reactionKillRate.
K2 is reactionFeedRate.
Scientists know what these are. But I would only expect to see variables like this in some bizarre nested loop, and I would consider it a code smell.
The inboundFlow "line" has a lot going on with little explanation (except in comments). The calculation is already happening and going into memory. Why not name that memory with variables?
Things like adjacentFlow and diagonalFlow to essentially name those respective lines.
Could even have adjacentFlowWeight and diagonalFlowWeight for some of those "magic numbers".
Comments shouldn't explain what is happening, but why it's happening.
The code already explains what is happening.
So a comment indicating what the overall formula is, how that relates to the used variables, then the variables essentially explain what each part of it is.
If a line is getting too complicated to be easily understood, then parting it out into further variables (or even function call, tho not applicable here) will help.
I would put in an editted example, however I'm on mobile and I know I will mess up the formatting.
A final style note, however I'm not certain on this.
I presume 1. and 1.0 are identical representing the float value of 1.0?
In which case, standardise to 1.0
There are instances of 2.0 and 2.
While both are functionally identical, something like (1.0, 1.0, 1.0) is going to be easier to spot that these are floats, as well as spotting typos/commas - when compared to (1., 1., 1.,).
IMO, at least
The only way to look after land is to build a parking lot or use it to add another lane to a 32 lane highway.
You can get off with just a fine if you dig up the land and put down lawn turf. The fine is reduced if you use 5 gallons a day of water to keep it green.
(/s)