Massimiliano Galli
Massimiliano Galli
Hi! I don't know if this can be useful, but a while ago I started working on @alexander-held's [repo](https://github.com/alexander-held/datacard-to-pyhf) with the intention of adding support for shape-based analyses datacards. You...
@oshadura it looks like there was already an issue for what we just discussed, so I will write down the summary here. I tried to connect to the jupyter hub...
Here it is: ``` $ condor_q -long 2576278.0 AccountingGroup = "group_u_CMS.u_zh.users.gallim" Args = "0" AutoClusterAttrs = "_condor_RequestCpus,_condor_RequestDisk,_condor_RequestMemory,AccountingGroup,BeerJob,BigMemJob,condor,JobUniverse,LastCheckpointPlatform,MachineLastMatchTime,MaxRuntime,MISSING,NumCkpts,Partit ionableSlot,Rank,RemoteOwner,RequestCpus,RequestDisk,RequestGPUs,RequestMemory,SendCredential,SlotID,TotalJobRuntime,WantExternalCloud,WantPreempt,x509UserProxyVOName,ConcurrencyLimits,NiceUser,Requirements,Charge Group,hdd,ssd,HammerCloudJob,NODE_IS_HEALTHY,InStagedDrain,ShutdownTime,NA61Test,WantIPv6Only,Memory,CvmfsCustomExpression,PreAfsRequirements,PreCvmfsRequirements,PreVerRequirements,VanillaRequirements" AutoClusterId = 39612 CernFlagDeprecatedSLC6 = false ChargeGroup = "cms" ChargeGroupType =...
Sure, here it is: ``` $ condor_q -better-analyze 2592991.0 -- Schedd: bigbird19.cern.ch : = RequestDisk) && (TARGET.Memory >= RequestMemory) && (TARGET.HasFileTransfer) PreVerRequirements = (NODE_MOUNTS_CVMFS || CvmfsCustomExpression) && PreCvmfsRequirements RequestDisk =...
I set ```HTMAP_DIR``` to ```/tmp/gallim/htmap``` but I get the same result (same error raised and jobs submitted but kept in idle)
Hi, is there any update on this?
> @amadio gave us an alternative in [xrootd/xrootd#2304 (comment)](https://github.com/xrootd/xrootd/issues/2304#issuecomment-2273394816), which can replace > > https://github.com/scikit-hep/uproot5/blob/aa8b94f722982c6eb418f9f32273152039836fb2/src/uproot/sink/file.py#L70-L81 > > (which [calls truncate in fsspec-xrootd](https://github.com/CoffeaTeam/fsspec-xrootd/blob/784540ce92f5b0bf3978a1410a70975f8838f3d2/src/fsspec_xrootd/xrootd.py#L374-L389)). It is only ever called from > >...
Hi Nick, I came back to this, doing some investigation and trying to follow your suggestion. However, there are a few things I don't understand. If I try to first...
> Ah, this might be a mistake, perhaps we can allow `a` mode? Though, with `a` we can only append. I'm not sure what the comment `update "+" mode removed...
This seems to come from fsspec, more precisely [here](https://github.com/fsspec/filesystem_spec/blob/fe59f48363029a0da68a0de534bf63e1c42e5a81/fsspec/core.py#L331-L366). It seems to me that it happens because the code doesn't distinguish between the ```::``` being part of the file name...