The files containing the instances have the following format:

NAME : <name of instance>
HORIZON : <number of days in the time horizon>
SUBPERIODS : <number of possible SPs>
SUBPERIODS_LIST : 
<s> days: <d1> <d2> ...
.
.
.
VERTICES : <number of vertices>
REQUIRED_LINKS : <number of required links>
NOT_REQUIRED_LINKS : <number of non-required links>
REQUIRED_LINKS_LIST :
(<u>,<v>) <link_type> serv_cost <c1> trav_cost <c2> subpds_fs: <s1> <f1> <s2> <f2> ...
.
.
.
NOT_REQUIRED_LINKS_LIST :
(<u>,<v>) <link_type> trav_cost <c2>
.
.
. 


SUBPERIODS_LIST is composed by entries "<s> days: <d1> <d2> ...", 
where s represents the SP index, whereas the days that compose each SP are listed after "days:".

REQUIRED_LINKS_LIST is composed by entries "(<u>,<v>) <link_type> serv_cost <c1> trav_cost <c2> subpds_fs: <s1> <f1> <s2> <f2> ...",
where u and v represent the indices of the endpoints of the link and link_type its typology (i.e., edge or arc). 
In addition, c1 and c2 are the costs for serving and traversing the link, respectively. 
Finally, s1 and f1 denote the first SP index associated with the link and its frequency, respectively, s2 and f2 denote the second SP index associated with the link and its frequency, respectively, and so on.   

NOT_REQUIRED_LINKS_LIST is composed by similar entries. 
In this case, the cost for serving the link and the sequence composed by the SPs/frequencies do not appear. 

Note that the instances appear with a lightly different names in the articles where they were introduced. 
In particular, pc_mval1A_f corresponds to pcp1-mval1A, pc_s_mval1A_f corresponds to pcp2-mval1A, pr_mval1A_f corresponds to prp1-mval1A, pr_s_mval1A_f corresponds to prp2-mval1A, and so on.