radioactive | Java 8 library for mutating beans | Build Tool library

You can try this tidyverse answer.

I have replaced NA in Dispose date with Creation date and for each row create a sequence of Dates from Creation date to Dispose date and store it in a list which can be unlisted in separate rows using unnest.

Use split and map. To save the plots as png you can include ggsave.

You're better off just using the secrets module for "real" randomness. This provides you with data from your kernel's CSPRNG, which should be constantly be gathering and mixing in new entropy in a way designed to make life very hard of any attacker.

Your use of infinite isn't appropriate either, you can't run something for "infinitely long" the heat death of the universe will happen a long time before then.

Using the standard Mersenne Twister (as Python's random module does) also seems inappropriate, as an attacker can recover the state after drawing just 624 variates. Using a CSPRNG would make this much harder, and constantly mixing in new state, as your kernel probably does, further hardens this.

Finally, treating the samples as floats then taking the mean and standard-deviation doesn't seem appropriate. You'd be much better off leaving them as ints and just passing them through a cryptographic hash. For example:

The easiest way to get the timeRemaining exposed to other classes is using the static keyword.

public static float timeRemaining = 10;

By making the variable static, it can be referenced by other classes. If you would rather not expose the variable completely, you can make static setter/getters. The variable would then be private static float timeRemaining = 10; when using the setter/getter.

You can specify weights with the weights parameter. To give more weight to values with small uncertainties use for instance 1/uncertainty.
The problem with your uncertainties in the example is, however, that they directly depend on the values of the amplitude (uncertainty=np.sqrt(amps)). If you use such kinds of uncertainties they will just shift your fitted curve downwards. So this approach only makes sense if your uncertainties are real uncertainties obtained from some kind of measurement.

Example:

Check the denominator in the first answer - you have (l1 - l2), whereas in the second result you have (l2 - l1). The results are then the same - easy to miss though!

First diagram (first version on the question)

Your generalizations if they exist are in the wrong direction, currently a Field is a Trapped and a Radioactive and an Entity is a E1 and a E2, but you wanted the reverse.

Anyway there is nothing in the statement saying a field cannot be both trapped and radioactive, in that case rather than to use generalizations better to use properties.

For the Entities it seems there are only E1 and E2 so you can use generalization (in reverse direction)

Second diagram

Note if Radioactive implements a Timer that means someone else has to kick each Radioactive and only them (no other Field).

Concerning the time to die, if it is the same whatever the instance of E1 and Radioactive that attribute can be static.

I do not understand the operation KillEntity because the moment an E1 is killed depends on when each instance enter in the field so cannot be general

You can handle the delay to die for a Field in a Radioactive in that least, for instance :

• each time an Entity enter in a Radioactive the Entity is added in dying for instance initializing duration to 0
• each time an Entity exit in a Radioactive the Entity is removed in dying
• each time tick is called each duration is increased and when becoming timeToDie the corresponding Entity is removed from dying and the operation die called on it
• the operation dies does noting on Entity but on E2 indicates the instance is killed (it is also possible to have that operation abstract on Entity and defined but doing nothing on E1)

Note you can replace the class-association by an association with a qualifier valuing the duration etc

But you can also handle the delay to die in E2 :

• tick on Entity/E2 is applied by a Radioactive on its Fields each time it is itself ticked, tick does nothing on Entity but manages the duration on E2 to kill the instance after the required delay (a static attribute can be shown again)

• each time an E2 moves to a new Field the duration is reset to 0

Note your multiplicity 1..* is wrong because a Field may not have Entity, on the opposite side the multiplicity is 1 if a dead E2 stay in a Radioactive else 0..1

The simpler the better. Without specific behavior in the statement depending on the extracted substance it is enough to have only one class Mine, and the the list of possible substances being known an enumeration is enough. Because a mine produces only one substance the multiplicity is 1.

The statement doesn't say if the mine can both be radioactive and collapse or not.

Supposing a mine can both be radioactive and can collapse, you can use an attribute for each danger:

It is also possible to use a enumeration for the danger and the multiplicity 0..2 but it is also necessary to have a constraint saying each danger appears at most one time, so this is not a simple way.

Else if even less probable a mine can have at most one danger you can again use a enumeration with the multiplicity 1:

or with the multiplicity 0..1:

You can use the following RegEx to match everything except