Upload eval/rabbit_eval_base.txt with huggingface_hub

eval/rabbit_eval_base.txt

@@ -0,0 +1,13 @@
+Found 25 corpora: ['camel_biology', 'camel_chemistry', 'camel_physics', 'rabbit_e2_phase0', 'rabbit_e2_phase1', 'rabbit_e2_phase2', 'rabbit_e2_phase3', 'rabbit_e2_phase4', 'rabbit_e2_phase5', 'rabbit_e2_phase6', 'rabbit_phase0', 'rabbit_phase1', 'rabbit_phase2', 'rabbit_phase3', 'rabbit_phase4', 'rabbit_phase5', 'rabbit_phase6', 'rabbit_phase7', 'raccoon_phase0', 'raccoon_phase1', 'raccoon_phase2', 'raccoon_phase3', 'raccoon_phase4', 'raccoon_phase5', 'raccoon_phase6']
+
+Loading tokenizer...
+
+Loading Pearl from /data/rabbit/scholar-efs/pearl
+  Pearl step: 1500
+  Layout: full
+  Weights: /data/rabbit/scholar-efs/pearl/weights_step1500.pt
+/home/ubuntu/rtaforge-substrates/white_rabbit/eval_rabbit.py:125: FutureWarning: You are using `torch.load` with `weights_only=False` (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for `weights_only` will be flipped to `True`. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via `torch.serialization.add_safe_globals`. We recommend you start setting `weights_only=True` for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
+  sd = unwrap_state_dict(torch.load(weights_path, map_location="cpu"))
+  Keys: 6850
+
+Creating model (vocab=50280, variant=fu-64)...