fixed and added more details in comments

Author: kishore-nori

src/CellData/SkeletonCellFieldPair.jl

@@ -68,16 +68,16 @@ function get_triangulation(a::SkeletonCellFieldPair)
 end
 
 #=
-We arbitrarily choose plus side of SkeletonCellFieldPair for evaluations, as
-we don't use the DomainContributions associated with Ω and Γ while performing
-the sensitivities for SkeletonTriangulation (Λ) DomainContribution. This
-fix is for error free evaluation of the functional when a SkeletonCellFieldPair
-is passed into it. Ideally, if we could parse and extract only the Skeleton
-integration terms from the functional's julia function form, this fix is not
-required, but this is not trivial to do. On the positive side, since the
-evaluations are all lazy and not used, this doesn't put any noticable memory
-or computational overhead. Ofcourse, it is made sure that the such plus side
-pick doesn't happen when the integration over the SkeletonTriangulation
+We arbitrarily choose plus side of SkeletonCellFieldPair for evaluations, as we
+don't use the DomainContributions associated with Ω and Γ while performing the
+sensitivities for SkeletonTriangulation (Λ) DomainContribution. This fix is for
+error free evaluation of the functional when a SkeletonCellFieldPair is passed
+into it. Ideally, if we could parse and extract only the Skeleton integration
+terms from the functional's julia function form, this fix is not required, but
+this is not trivial to do. On the positive side, since the evaluations are all
+lazy and not used, this doesn't put any noticable memory or computational
+overhead. Ofcourse, it is made sure that the such plus side pick doesn't happen
+when the integration over the SkeletonTriangulation
 =#
 # If SkeletonCellFieldPair is evaluated we just pick the plus side parent
 function evaluate!(cache,f::SkeletonCellFieldPair,x::CellPoint)
@@ -88,22 +88,34 @@ function evaluate!(cache,f::SkeletonCellFieldPair,x::CellPoint)
 end
 
 #=
-Fix for CellFieldAt{T}(parent::OperationCellField) for OperationCellField involving args which are not FEFunctions. It creates a problem with SkeletonCellFieldPair giving the wrong output or errors as it chooses the SkeletonCellFieldPair directly as the parent rather the parent CellField of the side of choice. In code terms it is the following:
+Fix for CellFieldAt{T}(parent::OperationCellField) for OperationCellField
+involving args which are not FEFunctions. It creates a problem with
+SkeletonCellFieldPair giving the wrong output or errors as it chooses the
+SkeletonCellFieldPair directly as the parent rather the parent CellField of the
+side of choice. In code terms it is the following:
 
 CellFieldAt{T}(OperationCellField) results in calling CellFieldAt{T}(operands).
-Without this override, CellFieldAt{T}(a::SkeletonCellField) results in the CellFieldAt structure with parent as SkeletonCellField and not a.T side CellField, which is not correct! This resulting in errors and is not the intended behaviour to have the parent as SkeletonCellFieldPair and is not consistent with our getproperty rules.
+Without this override, CellFieldAt{T}(a::SkeletonCellField) results in the
+CellFieldAt structure with parent as SkeletonCellField and not a.T side
+CellField, which is not correct! This resulting in errors and is not the
+intended behaviour to have the parent as SkeletonCellFieldPair and is not
+consistent with our getproperty rules.
 =#
 function CellFieldAt{T}(parent::SkeletonCellFieldPair) where T
   getproperty(parent,T)
 end
 
-# to handle the evaluation of SkeletonCellFieldPair at BoundaryTriangulation
-# making it consistent with plus side choice of direct evaluation of SCFP
-# in general this is the case when trian of CellField is not the same as
-# that of the quadrature
-# But we are protected from inconsistent behaviour at SkeletonTriangulation
-# as it fails due to the ambiguity as the CellField at the SkeletonTrian
-# for direct evaluations
+#=
+To handle the evaluation of SkeletonCellFieldPair at BoundaryTriangulation
+making it consistent with plus side choice of direct evaluation of SCFP in
+general this is the case when trian of CellField is not the same as that of the
+quadrature.
+But we are protected from inconsistent behaviour at SkeletonTriangulation as it
+fails due to similar ambiguity as the CellField at the SkeletonTrian for direct
+evaluations, so get_data doesn't create any side effects.
+In case of BodyFittedTriangulation there is no hit to get_data directly and
+evaluate! handles it as intended
+=#
 get_data(a::SkeletonCellFieldPair) = get_data(a.plus)
 
 function Base.propertynames(a::SkeletonCellFieldPair, private::Bool=false)