In order to enable an iCal export link, your account needs to have an API key created. This key enables other applications to access data from within Indico even when you are neither using nor logged into the Indico system yourself with the link provided. Once created, you can manage your key at any time by going to 'My Profile' and looking under the tab entitled 'HTTP API'. Further information about HTTP API keys can be found in the Indico documentation.
Additionally to having an API key associated with your account, exporting private event information requires the usage of a persistent signature. This enables API URLs which do not expire after a few minutes so while the setting is active, anyone in possession of the link provided can access the information. Due to this, it is extremely important that you keep these links private and for your use only. If you think someone else may have acquired access to a link using this key in the future, you must immediately create a new key pair on the 'My Profile' page under the 'HTTP API' and update the iCalendar links afterwards.
Permanent link for public information only:
Permanent link for all public and protected information:
- Do we want a tool for users or devs, which can tell us the (I/O) performance of the setup (software + hardware)? (conclusion: we want a global ROOT I/O instrumentation)
- Do we want the tool to have many knobs or just a few? Everything configurable, not at all or sensible defaults? (rather less than more)
- We want a mechanic for RNtuple to get the reads in a file for sequential entries (2D plot of reads for location in file)
- Do we want a tool that gives recommendations to improve the throughput or just performance metrics?
- It seems like the dev questions to root-readspeed are different than the user questions. Do we want two different tools?
-> We want definitely a user focused tool, like root-readspeed, to answer for the analyst what blocks the analysis (decompression, network, ...)
- Do we want root-readspeed as standalone tool or an instrumentation of RDataFrame?
-> We want an instrumentation of ROOT, without touching the user code, to get such metrics!
- Conclusion (for now): We want a TTreePerfStats-like global instrumentation of the ROOT I/O, to be enabled in a debug mode.
- TTree: Should be possible without large-scale changes
- RNtuple: Only vaguely planned
- Favored solution would be an environment variable and a perf-like output file, which can be nicely visualized later.
- Still, root-readspeed is also a perfect tool to get the very best I/O throughput (e.g. just sequential reads)