Job name too long for G5K or Enoslib

Created by: dimiarbre

There seems to be a size limit to job names, either from enoslib or g5k. Find what the limit is and where it is, and either:

• Circumvent the problem if it's possible (e.g. an enoslib limitation)
• Otherwise, avoid the problem. An idea is a dictionary-based solution: detect if the name is too long, hash it, run the experiments, and rename everything with the real name afterward.

Example of job name that is too long (by 1 character): zerosum_selfnoise_64nodes_1avgsteps_128th_static_seed90_degree4_RNET_lr0.01_1rounds