Perform various data analysis on SEC 13-F and obtain some insights of fund activities such as number of holdings, AUM, and change of holdings between two quarters.
日本語の概要は準備中です。原文の説明を表示しています。
Choose placements that preserve useful residual capacity. Use for bin packing, GPU sharing, accelerator placement, and multi-resource scheduling where stranded capacity hurts future fit.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when several feasible placements exist and the choice affects future capacity.
A placement is not good just because it fits. Good placements preserve useful residual capacity. With fractional GPUs, this often means packing small compatible jobs together while preserving whole or scarce GPU slots. The same idea applies to any slots, bins, or resources with discrete capacities.
For each feasible placement, compute a local before/after estimate:
fragmentation_before.fragmentation_after.marginal_fragmentation = fragmentation_after - fragmentation_before.best = None
for placement in feasible_placements:
target_before = copy(target_state)
fragmentation_before = estimate_fragmentation(target_before, workload_types)
target_after = apply(placement, target_before)
fragmentation_after = estimate_fragmentation(target_after, workload_types)
marginal_fragmentation = fragmentation_after - fragmentation_before
score = weighted_action_score(
marginal_fragmentation=marginal_fragmentation,
other_component_deltas=estimate_other_deltas(placement)
)
best = lower_score(best, placement, score)
choose best
Respect hard feasibility first. Use marginal_fragmentation as an input to the weighted action score, not as the only decision rule.
When workload shape probabilities are available, such as workload_types from cluster_config.json, use them to estimate which free capacity is likely to be useful:
fragmentation = 0
for workload_type in workload_types_from_cluster_config:
if workload_type.gpu_type is incompatible with target.gpu_type:
continue
can_fit =
target.cpu_free >= workload_type.cpu_units
and target.memory_free >= workload_type.memory_units
and any(slot.free_gpu_units >= workload_type.gpu_units
for slot in target.gpu_slots)
compatible_free_gpu = sum(slot.free_gpu_units for slot in target.gpu_slots)
if not can_fit:
fragmentation += workload_type.probability * compatible_free_gpu
else:
small_fragments = sum(
slot.free_gpu_units
for slot in target.gpu_slots
if 0 < slot.free_gpu_units < workload_type.gpu_units
)
fragmentation += workload_type.probability * small_fragments
If two 50-unit GPU jobs can share one 100-unit GPU slot, placing both on the same slot leaves another full slot free. Placing them on two separate slots creates two 50-unit leftovers, which may be harder for future 75- or 100-unit jobs to use.
The same pattern appears outside GPUs: two small tasks may belong in one bin so another bin remains available for a large task. When scores are close, use stable tie-breaks such as urgency, priority, smaller harmless leftovers, and deterministic target order.
Fragmentation is one objective component. A placement with slightly worse fragmentation may still be better if it substantially improves another weighted component, such as waiting, lateness, resource activation, or unserved-work cost. Conversely, a placement with excellent fragmentation may be bad if it causes a large cost elsewhere.
Use the before/after fragmentation estimate as one delta in a general score:
weighted_marginal_score =
fragmentation_weight * marginal_fragmentation
+ other_weight_1 * delta_other_component_1
+ other_weight_2 * delta_other_component_2
+ deterministic_tie_break
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Perform various data analysis on SEC 13-F and obtain some insights of fund activities such as number of holdings, AUM, and change of holdings between two quarters.
日本語の概要は準備中です。原文の説明を表示しています。
AC branch pi-model power flow equations (P/Q and |S|) with transformer tap ratio and phase shift, matching `acopf-math-model.md` and MATPOWER branch fields. Use when computing branch flows in either direction, aggregating bus injections for nodal balance, checking MVA (rateA) limits, computing branch loading %, or debugging sign/units issues in AC power flow.
日本語の概要は準備中です。原文の説明を表示しています。
Redact text from PDF documents for blind review anonymization
日本語の概要は準備中です。原文の説明を表示しています。
Use when checking simplified ADA-derived plan-view bathroom accessibility constraints such as turning space, door clear width, toilet centerline, grab bars, and lavatory knee/toe clearance.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze failed GitHub Action jobs for a pull request.
日本語の概要は準備中です。原文の説明を表示しています。
Use when extracting plan-view architectural geometry from DXF files with semantic CAD layers, especially when outputs must normalize rooms, doors, fixtures, clearances, and grab bars into machine-checkable JSON.
日本語の概要は準備中です。原文の説明を表示しています。