Changes

Jump to navigation Jump to search
no edit summary
==How to run==
In master.m, edit the options section to reflect what you want the code to do. Then run it, probably.
==Location/structure of the code==
The new codebase is located in
E:\McNair\Projects\MatchingEntrepsToVC\AdjustedCode
The new-new codebase is located in
E:\McNair\Projects\MatchingEntrepsToVC\ReAdjustedCode
 
Some of this code is just library code (prefix mtimesx).
===master.m===
====globals section====
dunno what this does
====options section====
* patternsearch
* cmaes
 
==Location/Structure of Data==
Pro tip: running the command
whos -file filename
from a matlab session will tell you the contents of any .mat file.
 
There are two of both psdata and dyad_tech_mkt_data, corresponding to 4 industries or 5 industries. You can find them in
E:\McNair\Projects\MatchingEntrepsToVC\OriginalCode\FVEIC4 data
and
E:\McNair\Projects\MatchingEntrepsToVC\OriginalCode\FVEIC5 data
 
'''psdata.mat''' contains
*vc: the number of VC's in each market, in the form of (10, 12, 13, ...): the first market has 10 VC's, the second market has 12 VC's....
*firm: the number of firms in each market, (13, 14, ...): the first market has 13 downstream, the second 14 downstream... this is a one (VC) to many (firms) market, and the number of firms in each market is at least as many as the number of firms
*m_id: unused, I'm guessing the market id
 
'''dyad_tech_mkt_data.mat''' variables used include:
*pvc_exp_n, mean_pvc_exp_n, std_pvc_exp_n
*lnfpat, mean_lnfpat:
*mean_m_dist_1000, std_m_dist_1000:
*mean_exp_sector, std_exp_sector:
*m_match: contains the matching outcome: for each dyad (firm VC pair), 0 means not matched and 1 means matched. The variable asg in the code contains the matching outcomes of all markets. The matching outcomes are delineated by firms using the position data N1 (vc' from psdata)and N2 (firm' from psdata).
 
 
==Location/Structure of Output==
226

edits

Navigation menu