Fix peformance issue with get_resolution

The code was unnecessarily checking the consistency of a single time
series resolution in calls to get_time_series. The check occurs when
the array is added to the system.

src/single_time_series.jl

@@ -44,7 +44,7 @@ function SingleTimeSeries(;
     return SingleTimeSeries(
         name,
         data,
-        _get_resolution(data),
+        get_resolution(data),
         scaling_factor_multiplier,
         internal,
     )
@@ -72,17 +72,6 @@ function SingleTimeSeries(
     )
 end
 
-function _get_resolution(data::TimeSeries.TimeArray)
-    if length(data) < 2
-        throw(
-            ConflictingInputsError(
-                "Resolution can't be inferred from the data. Please select an appropiate constructor.",
-            ),
-        )
-    end
-    return TimeSeries.timestamp(data)[2] - TimeSeries.timestamp(data)[1]
-end
-
 """
 Construct SingleTimeSeries from a TimeArray or DataFrame.
 

src/utils/utils.jl

@@ -384,12 +384,18 @@ end
 """
 Return the resolution from a TimeArray.
 """
-function get_resolution(ts::TimeSeries.TimeArray)
+function get_resolution(ts::TimeSeries.TimeArray; check_consistency = false)
+    if length(ts) < 2
+        throw(ConflictingInputsError("Resolution can't be inferred from the data."))
+    end
+
+    if !check_consistency
+        return TimeSeries.timestamp(ts)[2] - TimeSeries.timestamp(ts)[1]
+    end
+
     tstamps = TimeSeries.timestamp(ts)
     timediffs = unique([tstamps[ix] - tstamps[ix - 1] for ix in 2:length(tstamps)])
-
     res = []
-
     for timediff in timediffs
         if mod(timediff, Dates.Millisecond(Dates.Day(1))) == Dates.Millisecond(0)
             push!(res, Dates.Day(timediff / Dates.Millisecond(Dates.Day(1))))