Skip to content

Instantly share code, notes, and snippets.

View p3nGu1nZz's full-sized avatar
🌎
w o r k i n g • f r o m • s p a c e

p3ngu1nZz p3nGu1nZz

🌎
w o r k i n g • f r o m • s p a c e
View GitHub Profile
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Multiple Wobbly Plasma Bubbles</title>
</head>
<body>
@p3nGu1nZz
p3nGu1nZz / .py
Created December 2, 2024 14:14
EWC for fine-tuning models.
import torch
import torch.nn as nn
import torch.optim as optim
# Example model
class SimpleNN(nn.Module):
def __init__(self, input_size, hidden_size, output_size):
super(SimpleNN, self).__init__()
self.fc1 = nn.Linear(input_size, hidden_size)
self.fc2 = nn.Linear(hidden_size, output_size)
{"raw": "X-SPANFORMER\nSPAN-AwARE ENCODER\n5.4 Qualitative Span Interpretability\nTo assess the plausibility and semantic alignment of X-Spanformer's induced spans, we perform side-by-side comparisons against syntactic and semantic reference structures. Using single-sentence prompts drawn from the validation sets of WikiText and Stream-Mix, we visualize the top-K spans selected at various layers and entropy regimes. We benchmark span boundaries against:\nSyntactic parses: Constituents produced by Berkeley Neural Parser", "type": "mixed", "id": {"id": "a0409606-f532-4dd2-b02e-2a0bae5bfeee"}, "meta": {"status": "keep", "tags": [], "doc_language": "en", "extracted_by": "pdf2seg", "confidence": 0.78, "source_file": "XSpanformer_TokenizerFree_SpanAwareEncoder_RawsonChrzanowski_Preprint_v1.0_2025-06-26.pdf", "notes": "The segment contains a mix of technical terms and structured information that can be segmented into meaningful spans, such as \"X-SPANFORMER,\" \"SPAN-AwARE ENCODER,\" specific versions like \"5.4 Qua
Fantastic work, Claude! Love what we came up with—that’s exactly what people want. Let’s start by updating #file:ACTION_PLAN.md and deleting #file:M3_COMPLETION_TODO.md. Once that’s done, create a new file in the project root called TODO.md with an unordered [ ] to-do list containing short descriptions for each item (no nesting). Update the instructions in #file:copilot-instructions.md and #file:AGENTS.md to reflect this process. After updating the documentation, commit the changes to the current branch, push them, and then begin working on the tasks in TODO.md.