X-Git-Url: https://feistymeow.org/gitweb/?a=blobdiff_plain;f=scripts%2Fnotes%2Finfo_overload_report.sh;h=362be0cae33874fa1e7da1a39d2a28fbeb186fd9;hb=176dcb650f1dbefa08a342d83b4141ace594e05c;hp=57667e6ed8f3dbcf126fc23c2055ecf2a52b59c5;hpb=a251e17238618fdf2368ec57d3de1dd816086c0c;p=feisty_meow.git diff --git a/scripts/notes/info_overload_report.sh b/scripts/notes/info_overload_report.sh index 57667e6e..362be0ca 100644 --- a/scripts/notes/info_overload_report.sh +++ b/scripts/notes/info_overload_report.sh @@ -5,72 +5,137 @@ REPORT_FILE="$HOME/cloud/overload_history.txt" # 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() +function calculate_count() { local dir="$1"; shift - 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 ' ' + local count=$(find "$dir" -type f -exec echo \"{}\" ';' 2>/dev/null | grep -v "\.svn" | grep -v "\.git"| grep -v "\.basket" | grep -v "\.version" | grep -v "\.keep" | wc -l | tr -d ' ') + if [ -z "$count" ]; then echo 0; else echo "$count"; fi +} + +# calculates the size in kilobytes of all the note files in a hierarchy. +# this is just a raw statistic for how much content all those notes make up. since +# we have not separated out all the to-dos in some files (most notably the metaverse +# backlogs and to-do lists), it's good to also know what kind of girth the notes have. +function calculate_weight() +{ + local dir="$1"; shift + local weight=$(find "$dir" -type f -exec echo \"{}\" ';' 2>/dev/null | grep -v "\.svn" | grep -v "\.git"| grep -v "\.basket" | grep -v "\.version" | grep -v "\.keep" | xargs ls -al | awk '{ print $5 }' | paste -sd+ | bc 2>/dev/null) + if [ -z "$weight" ]; then echo 0; else echo "$weight"; fi +} + +# calculate_complexity gets a very simple metric of how many directory components are +# present at the target location and below. +function calculate_complexity() +{ + local dir="$1"; shift + local complexity=$(find "$dir" -type d | wc -l) + if [ -z "$complexity" ]; then echo 0; else echo "$complexity"; fi +} + +# produces a report line in our format. +function format_report_line() +{ + local count="$1"; shift + local weight="$1"; shift + weight=$((weight / 1024)) + local complexity="$1"; shift + echo "$count\t${complexity}\t\t${weight}\t\t$*\n" +} + +# two parameters are needed: the directory to sum up and the label to use for it in the report. +# this will calculate the count and weight for a hierarchy of notes, and then produce a +# line of reporting for those. +function analyze_hierarchy_and_report() +{ + local dir="$1"; shift + local label="$1"; shift + local count=$(calculate_count "$dir") + total_overload=$(($count + $total_overload)) + local weight=$(calculate_weight "$dir") + total_weight=$(($total_weight + $weight)) + local complexity=$(calculate_complexity "$dir") + total_complexity=$(($total_complexity + $complexity)) + full_report+=$(format_report_line "$count" "$weight" "$complexity" "$label") +} + +# scans through items in the notes folder that begin with a pattern. +# each of those is treated as an aggregable portion of the report. +# first parameter is the title in the report, second and so on are +# a list of directory patterns to scan and aggregate. +function analyze_by_dir_patterns() +{ + local title="$1"; shift + local hier_count=0 + local hier_weight=0 + local hier_complexity=0 + for folder in $@; do + temp_count=$(calculate_count $folder) + hier_count=$(($hier_count + $temp_count)) + temp_weight=$(calculate_weight $folder) + hier_weight=$(($hier_weight + $temp_weight)) + temp_complexity=$(calculate_complexity $folder) + hier_complexity=$(($hier_complexity + $temp_complexity)) + done + total_overload=$(($hier_count + $total_overload)) + total_weight=$(($total_weight + $hier_weight)) + total_complexity=$(($total_complexity + $hier_complexity)) + full_report+=$(format_report_line "$hier_count" "$hier_weight" "$hier_complexity" "$title") } ############## -# notes are individual files of tasks, usually, although some are combined. -note_depth=$(calculate_depth ~/cloud/grunty_notes) +# reset these before we add anything... +total_overload=0 +total_weight=0 -# unsorted files haven't been categorized yet. -unsorted_depth=$(calculate_depth ~/cloud/unsorted) +# start out the report with a header. +full_report="\ +\n\ +current information overload consists of:\n\ +\n\ +" +full_report+="count\tcomplexity\tweight (kb)\tcategory\n\ +================================================================\n\ +" -# source examples need to be sucked into other places, other codebases. they are not -# supposed to pile up here. -source_example_depth=$(calculate_depth ~/cloud/example_source) +analyze_hierarchy_and_report ~/cloud/urgent "high priority" -# the list files are web documents with to-do lists. individual items are marked with