Changes between Version 87 and Version 88 of WikiStart

Timestamp:

07/16/20 16:50:21 (5 years ago)

Author:

wouter

Comment:

--

WikiStart

@@ -101 +101 @@
 [[Image(tourtable.png, 80%)]]
 
+== Using hard coded profiles
+As mentioned on [https://tracinsy.ewi.tudelft.nl/pubtrac/GeniusWebProfilesServer#Getafilteredprofile the profilesserver wiki page] you can easily generate a partial profile out of an existing utilityspace. A big advantage of this is that [#Visualizingresultsinolderlogfiles the result plotters] can hack out the filter and use the utilityspace that the profile was generated from to show "hypothetical" utility values. However there are reasons not to do this, for example
+* A party getting the URL can easily hack out the filter option to gain access to the utilityspace 
+* Every time a websocket is created to the URL, a new, different filtered profile is generated. This may not fit the use case.
+
+Of course, profiles can also be written by hand to avoid this. However if that is done, [#Visualizingresultsinolderlogfiles the result plotters] can not apply this convenient trick anymore.
+
+If you want a hard fixed profile but keep the trick used by  the results plotters to remain working, an easy hack can be applied:
+ * create the utilityspaces that reflect your idealized/hypothetical  profile to be used by the result plotters
+ * [Download filtered profiles programmatically https://tracinsy.ewi.tudelft.nl/pubtrac/GeniusWebProfilesServer#Downloadingaprofileprogramatically] or write them by hand and store these on the server under a hashed name preventing recovery of the utilityspace name.
+ * run the parties with these hashed profiles
+ * after the run completes, manually edit the log files, replacing the hashed profilename with the original utilityapsce name. Make sure you make a backup of the log file, in case you screw up the replace.
+ * view the modified log file using the [#Visualizingresultsinolderlogfiles existing-log viewer]
+
+
 
 == Visualizing results in older log files