It’s a pity that I missed to mention it at the 1st of June: FastLEDs noise functions are out for more than a year now. So a late “happy birthday!” from my side.
I really like to encourage everybody to explore the functions - the matter is not as complex and difficult as it might appear on the first view. And the possibilities of it are widely underrated.
Here in the community we’ve seen the noise functions being used for colormappings, brightness and saturation masks, moving vectors, scaling effects, masks for constrained drawing, … there is sooo much to explore!
I’m not aware of any other algorithm which produces so organic and analogue appearing effects. It’s absolutely worth to give it a try! Just start with the examples showing the use of inoise8 and inoise16 and start using it! Play with it, explore it, abuse it, try to copy animations you’ve seen somewhere, try coding something unique you’ve never seen before - you will be surprised and amazed how beautiful the results can be! No matter if you work with 1, 2 or 3d setups.
Again: it’s not half as difficult to use the simplex noise as it appears. But the results can be really pleasing far beyond expectations…
@Daniel_Garcia : Thank you very much again for bringing this gift into the library!
Here the original announcement again because I liked the trailer so much:
https://plus.google.com/102282558639672545743/posts/h21fx1Zsp8V
In my videos you can see many different ways to use the simplex noise for very different animations - and I’m sure that I just scratched the surface of what’s possible yet!
So - before you code the next moving rainbow or chasing light - check out the examples and allow yourself to be surprised!
And allow us here in the community to be astonished by your results!
Thanks, cheers and GO! 
Combined with the Palette functionality in FastLED, the NoisePlusPalette.ino example demonstrates some awesome effects.
Yeah, definitely a huge thanks to Daniel and Mark for their work, but also to you, Stefan! Your patterns and effects are top notch!
Well, I’m basically just the guy who got a damn sharp knife in his hands and had some free time and playfullness to explore what’s possible to do with it beside cutting tomatos in quarters… @Mark_Kriegsman s color palettes and especially the crossfading between them was another major step in the librarys history worth to be honored at the release birthday. 
I’m not sure what you mean with “noise array declarations”.
In general I strongly reccomend to use a Teensy 3.1 for larger projects. Beside the RAM issue it’s also the calculation speed which is very limited on a 16Mhz AVR. How many leds are you going to drive?
1200 leds need a screenbuffer size of 3600 byte without any noise calculation. The Mega has 8k…
Go and get yourself a Teensy!
noise[MAX_DIMENSION][MAX_DIMENSION] can be replaced by your real height and width (in case your matrix is not quadratic).
I think it’s a good approach to render an animation into a “virtual matrix” and map that later onto the actual setup. So basically you can create a lookup table (or an algorithm) which describes which physical led(s) show the content of which virtual pixel. It’s also a good idea to mask out virtual pixels you are never going to use because so you can save time while rendering only the needed pixels. I used that method for example to map the content of a square matrix onto a circle of leds. Here in this example you see exactly the same animation - on the left side on 1024 leds and on the right side on 32 leds: https://www.youtube.com/watch?v=YGiwUqTeCSY Does that answer somehow you question?
It also works the other way arround (as you described it): every physical led number is linked to a x/y pair in the “virtual space”. By doing so you can skip the masking out and go while rendering just through all your x/y pairs. (in case your animations depends not on data of pixels arround like cellular automats) Sorry for my bad english today, I hope it makes sense anyway.
Maybe it would be helpfull to make a drawing/photo of your led setup and ask in a new post for other opinions how to manage the mapping.