Custom Node - create with initial parameters?

[forumg]

Hi everybody! 

First of all this is my first API experiment, so I am sorry for any stupid question that I am about to ask (And if that's the case thanks for your time and understanding) .

(Background)
I am creating a utility node, that will create some kind of noise (basically returns random like float values depending on the inputs). To calculate this random like values, I need an array of random values (like the gradient table in Perlin noise), and I create this array on fly every time a node is created, and I seed the random function with the current time. And it works okay. 

(Problem)
However, it is essential that each node of this type have different gradient tables(array of random values). When I create the nodes one by one, and create a scene with them, they work as I wanted, but when I save the scene and re-open it, they all produce the same results, because of the time seed I use to create array of random values. 

(What I want)
 Essentially I want my nodes to produce different results,  I want to somehow seed the random function of node once manually for each node I created, so they'll behave different even I close and open the scene again. 

Is there a way to creating the node with initial parameters? 

[joojaa]

I think, you have over engineered things a bit*. But yes just make a attribute called seed and mark it as file io only by setting its isFreeToChange to false.

In Normal maya philosophy ist considered the user front ends job to actually randomize the seed, this way the user CAN change the behaviour if they wish. And the usage experience need not be different (nothing says the users fronted cant do the seeding, its easier and more powerfull). Its having all the eggs in one basket. Since it doesent detract form user experience and makes your code easier and faster to make then it can only be the better course of action. So maya users may find your node somehow broken, this happens a lot.**

• your solving a problem wich you dont actually need to have.

**even if you think it best for user for you to take full controll over randomization there may be reasons for users to actually sample different noises, for example say they run several simulations to get the best possible solution. So they dont want to go trough the hasstle of recreating nodes jutst to get a new noise and off course they cant get it back if they need to except by reverting form save. They maya also have a clash in reference or  a reason to use same noise 2 times for some obscure reason.

Its not the node desighers job to tell users what the node is used for. Its the users job to do that. And they indeed will misuse your node the second they get a chance. So best play ball.