Added Block.scoreVideos method, along with a number of other utilities (a few of them denoted below), as well as the +workflow package that contains default functions for various parts of the scoring process that may be convenient to set on an ad hoc basis.
Note: The organization of Block.scoreVideos reflects the idea that for a given "behavioral trial," there would be at most one of any given kind of EventTimes event, as described below. The flexible configuration options should allow that framework to still properly accommodate most workflows.
Main Contribution
Block.scoreVideos can be configured to score a flexible number of behavioral parameters for two types of ScoredEvents: EventTimes and Meta.
EventTimes: Things like reach, grasp, support paw, etc. that have one "timestamp" associated per "trial."
Meta: Things such as the number of pellets on the platform, the outcome of the trial, etc.
+workflow contains several "template" default versions of functions that could easily be modified to accommodate other workflows. I'm probably a little bit too pleased with the nigeLab.workflow.defaultHotkeyHelpFcn...
Utilities
Added Scoring property to Block object, which is a struct that takes different Field elements as its fields. Scoring for Block.scoreVideos corresponds to the Video field of Block.Scoring. Inside that field, there is a table, where each row denotes a "session," for a given user. A session is considered as all the scoring (for a given user) that happened on a given day; if there are multiple instances where Block.scoreVideos was opened and closed on the same day by the same user, they get added together and it tracks the total time spent scoring.
Probably more usefully, there is a variable Status in the table that indicates the scoring status as either In Progress or Complete.
Added nigeLab.utils.getNigelDate to get current date (or convert a datenum) to a unified string.
Added nigeLab.utils.getNigeLink, which takes a function or class name as the first argument, a method or line number as the optional second argument, and an output string for the link as the optional third argument. It returns the formatted html command to link to the appropriate line in the Matlab editor for that code, which can be useful for debugging or for things like the hotkey help function.
Fixed a bug where nigeLab.libs.DiskData was not correctly getting data to the right place for Events files. This shouldn't have impacted past use (in Spikes and other ChannelsFieldType elements).
Description
Added
Block.scoreVideosmethod, along with a number of other utilities (a few of them denoted below), as well as the+workflowpackage that contains default functions for various parts of the scoring process that may be convenient to set on an ad hoc basis.Note: The organization of
Block.scoreVideosreflects the idea that for a given "behavioral trial," there would be at most one of any given kind ofEventTimesevent, as described below. The flexible configuration options should allow that framework to still properly accommodate most workflows.Main Contribution
Block.scoreVideoscan be configured to score a flexible number of behavioral parameters for two types of ScoredEvents:EventTimesandMeta.EventTimes: Things like reach, grasp, support paw, etc. that have one "timestamp" associated per "trial."Meta: Things such as the number of pellets on the platform, the outcome of the trial, etc.+workflowcontains several "template" default versions of functions that could easily be modified to accommodate other workflows. I'm probably a little bit too pleased with thenigeLab.workflow.defaultHotkeyHelpFcn...Utilities
Scoringproperty toBlockobject, which is a struct that takes differentFieldelements as its fields. Scoring forBlock.scoreVideoscorresponds to theVideofield ofBlock.Scoring. Inside that field, there is a table, where each row denotes a "session," for a given user. A session is considered as all the scoring (for a given user) that happened on a given day; if there are multiple instances whereBlock.scoreVideoswas opened and closed on the same day by the same user, they get added together and it tracks the total time spent scoring.Statusin the table that indicates the scoring status as eitherIn ProgressorComplete.nigeLab.utils.getNigelDateto get current date (or convert adatenum) to a unified string.nigeLab.utils.getNigeLink, which takes a function or class name as the first argument, a method or line number as the optional second argument, and an output string for the link as the optional third argument. It returns the formatted html command to link to the appropriate line in the Matlab editor for that code, which can be useful for debugging or for things like the hotkey help function.nigeLab.libs.DiskDatawas not correctly getting data to the right place forEventsfiles. This shouldn't have impacted past use (inSpikesand otherChannelsFieldType elements).