pegasus.cores causes issues on Summit

I wanted to let you know that specifying pegasus.cores in the TC can cause issues on Summit. Specifically, it results in CORES being defined as part of the +remote_cerequirements string. When this arrives on Summit, the CORES value is translated into a -n argument in the LSF script, but LSF on Summit doesn't support -n, and so the script submission fails. Since I think you also use pegasus.cores for metadata and such, I wanted to pass this on. Thanks!