…inhomogeneous tissue and ROfFx detector. Also performed code cleaned up on these two files. Since the ValidationResult.IsValid now returns true, simulation will proceed without interruption. This means that the ValidationRule set to "Warning: R(fx) theory assumes a homogeneous or layered tissue geometry" and the Remarks set to "User discretion advised" are not put to the screen since only results with IsValid=false put out these statements.

…ered-tissue-geometry

…ered-tissue-geometry

…ered-tissue-geometry and resolved conflicts:

#	src/Vts/MonteCarlo/DataStructuresValidation/SimulationInputValidation.cs

…ered-tissue-geometry

…ue and R(fx) detector specification to issue Warning and continue with simulation.

…ered-tissue-geometry

…the code, to issuing a warning and continuing on with the simulation.The philosophy here is that if combination of inputs is non-standard but the transport will not error, a warning is issued and the validation result remains true. This allows users to specify inconsistent combinations, e.g. angled source and cylindrical coordinate detectors, receive a warning and have the simulation proceed. If the combination of inputs will cause the transport to error, e.g. defining an embedded ellipsoid that overlaps with a tissue layer, then the input validation fails and the simulation stopped.

…dded unit test.

…r should not have a range.

…and floating point check.

…ck. Replaced Count() with Length and reduced long lines.

…ies in method names because not just incapabiities being checked, consistencies being checked too.