segment lengths calculated from cache files reguardless of skip-datafind in bayeswave-pipe

By not specifying the correct segment length, BayesWaveCleanFrame can segfault

This would fail if --cache-files weren't provided & --skip-datafind was on (which would fail earlier) Also fixes issue with the environment sourcing script that would append usr/bin to the front of the path

BayesWaveUtils/scripts/bayeswave_pipe

@@ -709,18 +709,10 @@ for ifo in ifo_list:
                 ldfcmd_file.writelines(ldfcmd+'\n\n')
             os.chmod(datafindscript, 0o755)
 
-        # Record frame segments so we can identify frames for osg_deploy transfers
-        if opts.skip_datafind:
-            # XXX: if no datafind, assume frames include jobs.  But should
-            # change to take cache file locations
-            frameSegs[ifo] = \
-                    segments.segmentlist([segments.segment(gps_start_time,
-                        gps_end_time)])
-        else:
-            frameSegs[ifo] = utils.fromlalcache(open(cache_files[ifo]))
-
-            if not frameSegs[ifo]:
-                raise ValueError("No frame data found with: {}".format(ldfcmd))
+        # get segment length of data from cache files 
+        frameSegs[ifo] = utils.fromlalcache(open(cache_files[ifo]))
+        if not frameSegs[ifo]:
+            raise ValueError("No frame data found with: {}".format(ldfcmd))
 
         if skip_segment_queries:
             segmentList[ifo] = \