added a couple more patterns for overload report.

[feisty_meow.git] / scripts / notes / info_overload_report.sh

diff --git a/scripts/notes/info_overload_report.sh b/scripts/notes/info_overload_report.sh
index 83ce152c888f7e1ca565b69c2476428279ae27de..80773324f3623277f110fc8389109ada27f3e9bd 100644 (file)
--- a/scripts/notes/info_overload_report.sh
+++ b/scripts/notes/info_overload_report.sh
@@ -1,13 +1,14 @@
 
 # these metrics are how bogged down we are in to-do type items.
 
-REPORT_FILE="$HOME/quartz/history_info_overload.txt"
+REPORT_FILE="$HOME/cloud/overload_history.txt"
 
-# given a path, this will find how many items are under it, ignoring svn and git files.
+# given a path, this will find how many items are under it, ignoring svn and git files, plus
+# other patterns we happen to notice are not useful.
 function calculate_depth()
 {
   local dir="$1"; shift
-  find "$dir" -type f -exec echo \"{}\" ';' | grep -v "\.svn" | grep -v "\.git" | wc -l | tr -d ' '
+  find "$dir" -type f -exec echo \"{}\" ';' |  grep -v "\.svn" | grep -v "\.git"| grep -v "\.basket" | grep -v "\.version" | grep -v "\.keep" | wc -l | tr -d ' '
 }
 
 ##############
@@ -20,36 +21,55 @@ unsorted_depth=$(calculate_depth ~/cloud/unsorted)
 
 # source examples need to be sucked into other places, other codebases.  they are not
 # supposed to pile up here.
-source_example_depth=$(calculate_depth ~/quartz/example_source_code)
+source_example_depth=$(calculate_depth ~/cloud/example_source)
 
 # the list files are web documents with to-do lists.  individual items are marked with <li>.
 item_depth=$(find ~/cloud/grunty_notes/ -type f -iname "*.html" -exec grep "<li" "{}" ';' | wc -l | tr -d ' ')
 
 # scan across all appropriately named folders in our folders that live in the "cloud".
-cloud_depth=0
+cloud_project_depth=0
 for i in ~/cloud/*project* ~/cloud/*research*; do
   temp_depth=$(calculate_depth $i)
-  cloud_depth=$(($cloud_depth + $temp_depth))
+  cloud_project_depth=$(($cloud_project_depth + $temp_depth))
 done
 
+# also snag the files labelled as trivia, since they're still to-dos...
+cloud_trivia_depth=0
+for i in ~/cloud/*trivia*; do
+  temp_depth=$(calculate_depth $i)
+  cloud_trivia_depth=$(($cloud_trivia_depth + $temp_depth))
+done
+
+# and then count up the things that we think will be cleaned soon, but one thing we have learned
+# is that things that are intended are not always followed up on right away.  this catches us
+# being too hopeful and makes sure nothing seems to be getting done that's lagging.
+cloud_active_depth=0
+for i in ~/cloud/*active*; do
+  temp_depth=$(calculate_depth $i)
+  cloud_active_depth=$(($cloud_active_depth + $temp_depth))
+done
+
+#hmmm: the find and add thing is starting to look like a useful function.
+
 ##############
 
-total_overload=$(($note_depth + $item_depth + $unsorted_depth + $source_example_depth + $cloud_depth))
+total_overload=$(($note_depth + $item_depth + $unsorted_depth + $source_example_depth + $cloud_project_depth + $cloud_trivia_depth + $cloud_active_depth))
 
 report="\
 \n\
 Current information overload consists of:\n\
+[gathered on $(date)]\n\
 \n\
-  $note_depth\tnote files\n\
+  $note_depth\tgrunty notes\n\
   $item_depth\tto-do list items\n\
-  $unsorted_depth\tunsorted files\n\
+  $cloud_active_depth\tactive items\n\
+  $cloud_project_depth\tproject files\n\
   $source_example_depth\tsource examples\n\
-  $cloud_depth\tcloud notes\n\
+  $cloud_trivia_depth\ttrivial notes\n\
+  $unsorted_depth\tunsorted files\n\
   -------\n\
   $total_overload\ttotal items\n\
 \n\
-Gathered On: $(date)\n\
-\n\
 ##############"
 
 echo -e "$report" | tee -a "$REPORT_FILE"