btch_dlg.dcl — Batch Processing Configuration¶
File: btch_dlg.dcl
Version: v3.60
Category: Dialog Definitions
Size: 8.5 KB (258 lines)
Note
Batch Panel Generation
Automate creation of multiple similar panels using template-based batch processing. Essential for large projects with many identical or similar panels.
Functional Purpose¶
Batch Panel Creation - Automates generation of multiple panels based on template panel, with automatic numbering, systematic variations, and bulk operations for efficiency in large projects.
Key Functions:
Uses template panel (fully configured existing panel)
Generates panel series (sequential numbering)
Applies systematic variations (dimensions, features)
Auto-increments panel numbers (P-101, P-102, P-103…)
Batch operations (create, modify, delete multiple panels)
Progress tracking (status display during generation)
User Need¶
Batch processing for:
Large projects (50+ panels, many similar)
Repetitive panels (typical floor plan, 10 floors = 200 panels)
Panel families (same design, different widths)
Time savings (minutes vs hours for manual creation)
Consistency (all panels use same template = fewer errors)
Project efficiency (reduce drafting time by 80%+)
Typical Workflow¶
1. User creates Template Panel (fully configured):
• Panel P-101: 12'×10'×6" wall panel
• 2 windows, 1 door
• All features, reinforcement configured
• Drawing generated and verified
2. User opens batch_dlg (from csvmenu or mp_dlg)
3. User selects template: P-101
4. User sets batch parameters:
• Start number: P-102
• End number: P-120
• Increment: 1 (P-102, P-103, P-104...)
• Total panels: 19 new panels
5. User selects variation type:
• Identical: All exactly like P-101
OR
• Width variation: 8', 10', 12', 14', 16' (cycle)
OR
• Custom: User-defined changes per panel
6. User clicks [Generate]
7. System creates panels:
• P-102: Copy P-101, rename
• P-103: Copy P-101, rename
• ... (progress bar shown)
• P-120: Copy P-101, rename
8. Result: 19 new panels in <1 minute (vs ~3 hours manual!)
Control Semantics¶
Template Selection¶
Source Panel:
btt- Template panel dropdown:List of all existing panels in project
User selects master/template panel
All features copied from this panel
Template Verification:
btv- Verify template button:Opens template panel for review
User confirms all features correct
“Fix template, then batch” workflow
Batch Range¶
Panel Numbering:
bts- Start panel number:Format: “P-102”, “W-201”, custom prefix
First panel in batch sequence
bte- End panel number:Format: “P-120”, “W-250”, etc.
Last panel in sequence
bti- Increment:1 (most common): P-101, P-102, P-103…
2 (by-twos): P-102, P-104, P-106…
10 (by-tens): P-110, P-120, P-130…
Custom: Any increment
Count Display:
btc- Panel count (calculated):Auto-calculated from start/end/increment
“19 panels will be created”
Warning if > 100 panels
Variation Options¶
Variation Type:
btv- Variation mode:Identical (Default):
All panels exactly like template
Fastest, simplest
Use when: Truly repetitive panels
Dimension Variation:
Panel dimensions change systematically
Example: Width cycles through 8’, 10’, 12’
Height changes: +1’ per floor (story height)
Thickness constant or varies
Feature Variation:
Opening positions shift
Window/door count changes
Feature enable/disable patterns
Custom Variation:
User provides variation schedule
CSV file or manual input
Panel-by-panel customization
Variation Parameters:
btvp- Variation parameters:Width list: “8, 10, 12, 14, 16” (cycle through)
Height increment: “+12” (add 1’ per panel)
Feature pattern: “ON, ON, OFF, ON” (repeating)
Batch Operations¶
Operation Type:
bto- Batch operation:Create (Most Common):
Generate new panels
From template
Add to project
Modify:
Update existing panels
Apply changes to range
Example: Change all P-101 to P-120 thickness to 8”
Renumber:
Change panel numbers
Old P-101?120 become P-201?220
Maintains all features
Delete:
Remove panel range
Confirmation required!
Cannot undo easily
Batch Processing Logic¶
Identical Batch (Simplest)¶
Algorithm:
Template: P-101 (12'×10'×6", 2 windows)
Range: P-102 to P-110 (9 panels)
For each panel number P-102 to P-110:
1. Copy all data from P-101
2. Change panel number to current (P-102, etc.)
3. Save panel to database
4. Generate drawing
5. Update progress bar
Result: 9 identical panels in ~30 seconds
Dimension Variation¶
Width Cycling:
Template: P-101 (12' wide)
Variation: Cycle widths [8', 10', 12', 14', 16']
Range: P-102 to P-120 (19 panels)
Panel Width
P-102 8' (first in cycle)
P-103 10' (second)
P-104 12' (third)
P-105 14' (fourth)
P-106 16' (fifth)
P-107 8' (cycle repeats)
P-108 10'
...
P-120 14' (19 mod 5 = 4th in cycle)
Algorithm:
For each panel:
width_index = (panel_index) mod (cycle_length)
panel_width = width_cycle[width_index]
copy_template_and_set_width(panel_width)
Height Increment¶
Story-Height Variation:
Template: P-101 (10' tall - first floor)
Variation: +12" per floor (story height = 12')
Range: P-102 to P-111 (10 panels = 10 floors)
Panel Floor Height
P-101 1 10' (template)
P-102 2 11' (10' + 1')
P-103 3 12' (10' + 2')
P-104 4 13' (10' + 3')
...
P-111 10 19' (10' + 9')
Use Case:
First floor: 10' (ground level, shorter)
Typical floors: 11'-12' (standard ceiling height)
Penthouse: 14'+ (luxury, higher ceilings)
Engineering Considerations¶
Time Savings¶
Manual vs Batch:
Manual Creation:
1 panel = 15 minutes (configure, verify, draw)
20 panels = 15 × 20 = 300 minutes = 5 hours
Batch Creation:
Template = 15 minutes (one-time)
Batch = 1 minute (automated)
20 panels = 16 minutes total
Savings: 284 minutes = 4.7 hours (94% reduction!)
Large Project:
10-story building, 20 panels/floor
Total: 200 panels
Manual: 200 × 15 min = 3,000 min = 50 hours
Batch: 15 min (template) + 10 min (batch) = 25 minutes
Savings: 49.6 hours (99.2% reduction!)
Cost savings: $2,500+ in labor @ $50/hr
Verification Requirements¶
Quality Control:
Critical: Verify template panel THOROUGHLY!
All batch panels inherit template errors
Checklist:
? Dimensions correct
? All openings properly sized/located
? Reinforcement adequate
? Connection details complete
? Material specifications correct
? Drawing generates properly
One template error × 200 panels = 200 errors to fix!
User Example¶
Scenario: 5-story office building, 16 panels per floor
1. Create Template: P-101 (Ground Floor)
• 12'×10'×6" wall panel
• 3 windows (4'×5' each)
• All features configured
• Drawing generated and approved
2. Batch Ground Floor (Panels 1-16):
• Template: P-101
• Range: P-102 to P-116 (15 more)
• Variation: Width cycles [8', 10', 12', 14']
• Result: 16 ground floor panels in 1 minute
3. Batch 2nd Floor (Panels 201-216):
• Template: P-101
• Range: P-201 to P-216
• Variation: Height +12" (typical floor = 11')
• Result: 16 second floor panels
4. Repeat for Floors 3-5:
• Batch 3: P-301 to P-316 (height +24")
• Batch 4: P-401 to P-416 (height +36")
• Batch 5: P-501 to P-516 (height +48")
5. Total:
• 80 panels created
• Time: ~10 minutes (including template)
• Manual equivalent: 20 hours!
Integration¶
Called By: csvmenu ? Batch or mp_dlg ? [Batch] Drawing: batch.lsp orchestrates panel creation and drawing generation
Variables:
batch-template- Source panel IDbatch-start- First panel numberbatch-end- Last panel numberbatch-increment- Numbering stepbatch-variation-type- Variation modebatch-variation-params- Variation parameters
Database Operations:
Reads template panel data
Creates new panel records
Updates panel_list xrecord
Generates drawings for each panel
Best Practices¶
Template Preparation:
? Fully configure and verify template first
? Generate drawing to confirm correctness
? Have template reviewed by engineer/QC
? Document any special features/notes
Batch Planning:
? Plan numbering scheme before starting
? Use consistent increments (1 or 10 typical)
? Group similar panels in ranges
? Reserve number blocks for special panels
Variation Strategy:
? Use identical batch when truly repetitive
? Use dimension variation for systematic changes
? Avoid excessive variation (defeats batch purpose)
? Review sample panels from batch before full run
Common Mistakes:
? Not verifying template (errors replicate!)
? Wrong numbering scheme (renumber later = pain)
? Too many variations (batch becomes complex)
? Not checking first few panels (catch errors early)
Documentation Metadata¶
Enhancement Status: ? COMPREHENSIVE - ENHANCED [5/8]
End of Document