Loading hmda records in file chunks

load_hmda command now takes directory argument where csv files split from hmda csv are located. This was done to reduce memory leak issues when opening a 3gb csv file. 
Can we call 'f' something more descriptive?