Merge pull request #251 from ldbc/add-interactive-sf3000

Add Interactive SF3000

legacy-data-sets.tex

@@ -48,13 +48,13 @@ \subsection{Scale Factors}
 For example, SF1 takes roughly 1~GiB in CSV format, SF3 weighs roughly 3~GiB and so on and so forth.
 It is important to note that for a given scale factor, data sets generated using different serializers contain exaclty the same data, the only difference is in how they are represented.%
 \footnote{Naturally, there are slight differences in the disk usage of the data sets created with different serializers. For example, for a given scale factor, the disk usage of the data set serialized with the CsvBasic serializer is expected to be higher, while with the CsvMergeForeignComposite, it is expected to be lower.}
-The provided SFs are the following: 1, 3, 10, 30, 100, 300, 1000.
-Additionally, two small data sets, 0.1, and 0.3 are provided to help initial validation efforts.
+The provided SFs are the following: \numprint{1}, \numprint{3}, \numprint{10}, \numprint{30}, \numprint{100}, \numprint{300}, \numprint{1000}, \numprint{3000}.
+Additionally, two small data sets, \numprint{0.1}, and \numprint{0.3} are provided to help initial validation efforts.
 
 The Test Sponsor may select the SF that better fits their needs, by properly configuring the \datagen, as described in \autoref{sec:data_generation}.
 The size of the resulting dataset is mainly affected by the following configuration parameters: the number of persons and the number of years simulated.
 By default, all SFs are defined over a period of three years, starting from 2010, and SFs are computed by scaling the number of Persons in the network.
-\autoref{tab:snsize-interactive} shows some metrics of SFs 0.1, \ldots, 1000 data sets.
+\autoref{tab:snsize-interactive} shows some metrics of SFs \numprint{0.1}, \ldots, \numprint{1000} data sets.
 
 \input{tables/legacy/table-snsize-interactive}