更新工作日志

.gitignore

@@ -3,3 +3,4 @@ reply.aer
 reply.csv
 warlock.log
 warlock-exception.log
+*.log

README.md

@@ -1,65 +1,3 @@
-**CUI**
+想定文件结构介绍
 
-# aea_iads demo
+基本结构
-
-This directory contains the necessary files to test the EW effects
-in a scenario similar to the iads_demo baseline scenario.
-
-The SOJ and EW_Radar have EA and EP techniques, respectively, with them
-to aid in the testing and verification of these techniques.
-
-The strike.txt file is the normal input file to run the simulation
-as a single application. The replay file will be written to the
-output directory.
-
-Also included are two realtime run files strike-rt.txt and iads-rt.txt
-that can be run concurrently to test the jamming and EW effects over DIS.
-Each WSF application communicates over DIS. The applications can be run
-on separate hosts or on the same host.  The file dis_data.txt provides
-the DIS Enumeration mapping for the entity types, emitter types, and ew
-technique types.
-
-To visually monitor the progress of the realtime simulations, Warlock can
-be opened and then configured to monitor multicast address 224.2.25.55, 
-port 3225 via an input file containing a dis_interface block.
-
-## CUI Designation Indicator
-* Controlled by: Air Force Research Laboratory
-* Controlled by: Aerospace Systems Directorate
-* CUI Categories: CTI, EXPT
-* LDC/Distribution Statement: DIST-C
-* POC: afrl.rq.afsim@us.af.mil
-
-## Notices and Warnings
-
-### DISTRIBUTION STATEMENT C
-Distribution authorized to US Government agencies and their contractors;
-Critical Technology, Export Controlled; (2021 Oct 06). Other requests for this
-information shall be referred to AFRL Aerospace Systems Directorate.
-
-### NOTICE TO ACCOMPANY FOREIGN DISCLOSURE
-This content is furnished on the condition that it will not be released to
-another nation without specific authority of the Department of the Air Force of
-the United States, that it will be used for military purposes only, that
-individual or corporate rights originating in the information, whether patented
-or not, will be respected, that the recipient will report promptly to the
-United States any known or suspected compromise, and that the information will
-be provided substantially the same degree of security afforded it by the
-Department of Defense of the United States. Also, regardless of any other
-markings on the document, it will not be downgraded or declassified without
-written approval from the originating U.S. agency.
-
-### WARNING - EXPORT CONTROLLED
-This content contains technical data whose export is restricted by the Arms
-Export Control Act (Title 22, U.S.C. Sec 2751 et seq.) or the Export
-Administration Act of 1979, as amended, Title 50 U.S.C., App. 2401 et seq.
-Violations of these export laws are subject to severe criminal penalties.
-Disseminate in accordance with provisions of DoD Directive 5230.25.
-
-### HANDLING AND DESTRUCTION NOTICE
-Handle this information in accordance with DoDI 5200.48. Destroy by any
-approved method that will prevent unauthorized disclosure or reconstruction of
-this information in accordance with NIST SP 800-88 and 32 C.F.R 2002.14
-(Safeguarding Controlled Unclassified Information).
-
-**CUI**

doc/diary/2025年12月3日.md

@@ -0,0 +1,37 @@
+# 开发步骤
+
+直接找人吧，重点是把场景搭建出来，需要知道差在哪里
+
+1. 定义出来，我写个模版，内容是怎么出来的，按照什么格式出数据
+2. 
+
+# 定义模版
+
+不允许存在继承（方便内容开发）
+
+# 我的问题
+
+1. 行为有啥区别？ 总共就三个？
+2. base_types ： 用到了什么，必须要提供给谁？如果没有了会影响到什么？
+   1. 
+3. 根目录的内容：
+4. 4个模版是怎么回事？我需要看看数据
+5. 通信怎么实现的
+6. 有没有介绍性的文档（我需要知道afsim 中的平台在场景中是怎么映射上的）
+7. 我需要删除不需要的内容（因为我需要提供给另外一个单位一个模版，这个模版需要是能解释的，当然也可以存在一些依赖库性质的内容，但是这些内容需要进行正确的解耦，不能说散在各个地方，比如说base_types 一个文件夹，是一个依赖，我们就不需要对他进行解释，但是不能每个文件夹下都有这种依赖（删掉没用的，实在删不掉，集中存放）
+8. patterns？platforms 删掉没用的平台，processors （是不是基本没用过）
+9.  scenarios ，blue 和red 分类很好，但是其他的几个是干啥的？
+10. 雷达的使用情况
+11. signature
+12. weapons 这个省下来，应该是不用动
+
+
+# 总结如下
+检查每个文件夹下，没用到的东西（因为后面需要用程序生成程序，不能这么混乱
+
+平台的使用，正常的情况下，一个武器应该是能够挂载在多个平台上面的，wj 的处理方式是新建，新建每一个平台，对应的武器名字加上平台的前缀。
+
+根目录精简，最后精简到一个，但是为了方便代码立即，可以适当减少修改
+
+
+

doc/diary/2025年12月4日.md

@@ -0,0 +1,16 @@
+
+TODO 
+1. 找出来base_types 用到的（0.5）
+2. 根目录的内容：做成重复的，改成setup（2）
+3. 4个模版（测试效果） (1个小时)
+4. 通信，整理，测试，主要是写文档，写一组例子（3个平台互相通信）（4）
+5. platforms 删掉没用的平台（1）
+6. processors(2)
+7. scenarios(1)
+8. 雷达的使用情况(2)
+9. weapons,整理一下，用到的（1）
+10. signature()
+
+
+# 梁雲
+1. 写一个能交差的场景，只需要包含几部分，空投空降，渗透侦查和通信保障

mission-exception.log

@@ -1,24 +0,0 @@
-########################################################################
-Wed Oct 22 01:06:45 2025
-
-Version: 2.9.0
-Compiler: win_1916_64bit_release-hwe
-Called std::terminate().
-Stacktrace:
-     0# 0x7ff901753371 (ut::WriteTerminateLog) at ??
-     1# 0x7ff901751b3d (ut::TerminateHandler) at ??
-     2# 0x7ff9860019d7 (terminate) at ??
-     3# 0x7ff97cf64c27 (WsfPluginVersion) at ??
-     4# 0x7ff8fe37825b (WsfArticulatedPart::WithinSlewLimits) at ??
-     5# 0x7ff8fe37823c (WsfArticulatedPart::WithinSlewLimits) at ??
-     6# 0x7ff8fe37b354 (UtGraphT<WsfPFNode,WsfPFEdge,0,double>::erase) at ??
-     7# 0x7ff8fe36857a (WsfExtensionList::~WsfExtensionList) at ??
-     8# 0x7ff8fe90d7e9 (WsfSimulation::~WsfSimulation) at ??
-     9# 0x7ff8fe89b43c (WsfPlatformPartEvent::~WsfPlatformPartEvent) at ??
-    10# 0x7ff6f37b2626 (<28><>ͼ<EFBFBD><CDBC><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Ч<EFBFBD>ĵ<EFBFBD>ַ<EFBFBD><D6B7>) at ??
-    11# 0x7ff6f37b3c02 (<28><>ͼ<EFBFBD><CDBC><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Ч<EFBFBD>ĵ<EFBFBD>ַ<EFBFBD><D6B7>) at ??
-    12# 0x7ff6f37b4364 (<28><>ͼ<EFBFBD><CDBC><EFBFBD><EFBFBD><EFBFBD><EFBFBD>Ч<EFBFBD>ĵ<EFBFBD>ַ<EFBFBD><D6B7>) at ??
-    13# 0x7ff987a3e8d7 (BaseThreadInitThunk) at ??
-    14# 0x7ff988c9c34c (RtlUserThreadStart) at ??
-
-

mission.log

@@ -1,81 +0,0 @@
-2025-10-22 01:22:30 file strike.txt
-2025-10-22 01:22:30 version wsf 2.9.0
-2025-10-22 01:22:30 file strike.txt
-2025-10-22 01:22:30 file setup.txt
-2025-10-22 01:22:30 file event_output.txt
-2025-10-22 01:22:30 file event_pipe.txt
-2025-10-22 01:22:30 file csv_event_output.txt
-2025-10-22 01:22:30 file terrain.txt
-2025-10-22 01:22:30 file platforms/common.txt
-2025-10-22 01:22:30 file platforms/cmdr_players.txt
-2025-10-22 01:22:30 file ./platforms/iads_cmdr.txt
-2025-10-22 01:22:30 file ./processors/commander_track_manager.txt
-2025-10-22 01:22:30 file ./platforms/red_radar_company.txt
-2025-10-22 01:22:30 file ./platforms/target.txt
-2025-10-22 01:22:30 file platforms/radar_players.txt
-2025-10-22 01:22:30 file ./platforms/red_radar.txt
-2025-10-22 01:22:30 file ./platforms/red_radar_tactics.txt
-2025-10-22 01:22:30 file ./platforms/ew_radar.txt
-2025-10-22 01:22:30 file ./sensors/radar/ew_radar.txt
-2025-10-22 01:22:30 file ./processors/ep_operations.txt
-2025-10-22 01:22:30 file ./platforms/acq_radar.txt
-2025-10-22 01:22:30 file ./sensors/radar/acq_radar.txt
-2025-10-22 01:22:30 file platforms/sam_players.txt
-2025-10-22 01:22:30 file ./platforms/large_sam_battalion.txt
-2025-10-22 01:22:30 file ./processors/red_sam_battery_tactics.txt
-2025-10-22 01:22:30 file ./weapons/sam/sam_launch_computer.txt
-2025-10-22 01:22:30 file ./weapons/sam/large_sam_launch_computer.txt
-2025-10-22 01:22:30 file ./platforms/large_sam_ttr.txt
-2025-10-22 01:22:30 file ./sensors/radar/ttr_radar.txt
-2025-10-22 01:22:30 file ./platforms/large_sam_launcher.txt
-2025-10-22 01:22:30 file ./weapons/sam/large_sam.txt
-2025-10-22 01:22:30 file ./behavior/behavior_fire.txt
-2025-10-22 01:22:30 file ./behavior/behavior_move.txt
-2025-10-22 01:22:30 file ./behavior/behavior_wait.txt
-2025-10-22 01:22:30 file platforms/blue_players.txt
-2025-10-22 01:22:30 file ./platforms/ucav.txt
-2025-10-22 01:22:30 file ./signatures/ucav_sigs.txt
-2025-10-22 01:22:30 file ./signatures/ucav_infrared_sig.txt
-2025-10-22 01:22:30 file ./signatures/ucav_optical_sig.txt
-2025-10-22 01:22:30 file ./signatures/ucav_radar_sig.txt
-2025-10-22 01:22:30 file ./sensors/esm_rwr/ucav_esm.txt
-2025-10-22 01:22:30 file ./sensors/radar/ucav_sar.txt
-2025-10-22 01:22:30 file ./weapons/agm/blue_gps_bomb_2.txt
-2025-10-22 01:22:30 file ./weapons/agm/blue_gps_bomb_1.txt
-2025-10-22 01:22:30 file ./weapons/agm/blue_glide_bomb_1.txt
-2025-10-22 01:22:30 file ./behavior/UCAV_fire.txt
-2025-10-22 01:22:30 file ./behavior/UCAV_move.txt
-2025-10-22 01:22:30 file ./behavior/UCAV_wait.txt
-2025-10-22 01:22:30 file ./platforms/soj.txt
-2025-10-22 01:22:30 file ./signatures/fighter_sigs.txt
-2025-10-22 01:22:30 file ./signatures/fighter_infrared_sig.txt
-2025-10-22 01:22:30 file ./signatures/fighter_optical_sig.txt
-2025-10-22 01:22:30 file ./signatures/fighter_radar_sig.txt
-2025-10-22 01:22:30 file ./weapons/jammer/soj_vhf_jammer.txt
-2025-10-22 01:22:30 file ././weapons/jammer/soj_base_jammer.txt
-2025-10-22 01:22:30 file ././weapons/jammer/false_target.txt
-2025-10-22 01:22:30 file ./weapons/jammer/soj_sband_jammer.txt
-2025-10-22 01:22:30 file ./weapons/jammer/soj_xband_jammer.txt
-2025-10-22 01:22:30 file platforms/radar_apache.txt
-2025-10-22 01:22:30 file scenarios/nets_zones.txt
-2025-10-22 01:22:30 file weapons/jammer/radar_jammer_2_18ghz.txt
-2025-10-22 01:22:30 file weapons/jammer/comm_jammer_30m_3g.txt
-2025-10-22 01:22:30 file platforms/blue/blue_ew_aircraft.txt
-2025-10-22 01:22:30 file scenarios/red.txt
-2025-10-22 01:22:30 file scenarios/blue.txt
-2025-10-22 01:22:30 file ./platforms/blue/TG3_missile.txt
-2025-10-22 01:22:30 file ./platforms/blue/TG3_radar.txt
-2025-10-22 01:22:30 file ./platforms/blue/TG3_cmdr.txt
-2025-10-22 01:22:30 file ./platforms/mortar.txt
-2025-10-22 01:22:30 file ./weapons/ssm/red_srbm_1.txt
-2025-10-22 01:22:30 file ./platforms/blue/m1a2t.txt
-2025-10-22 01:22:30 file ./platforms/blue/m60.txt
-2025-10-22 01:22:30 file ./platforms/blue/CM-32.txt
-2025-10-22 01:22:30 file scenarios\blue/defence_close.txt
-2025-10-22 01:22:30 file ./platforms/blue/anti_drone_mobile_radar.txt
-2025-10-22 01:22:30 file ./weapons/ssm/red_srbm_1_launch_data.txt
-2025-10-22 01:22:30 AER output file: output/strike.aer
-2025-10-22 01:22:30 Event output file: output/strike.evt
-2025-10-22 01:22:30 Event output file: output/strike.csv
-2025-10-22 01:22:30 start 1
-2025-10-22 01:22:31 complete 2400.000 0.694 1.391

warlock-exception.log

@@ -1,26 +0,0 @@
-########################################################################
-Tue Sep 23 10:13:24 2025
-
-Version: 2.9.0
-Compiler: win_1929_64bit_release-hwe
-The simulation threw an unhandled exception.
-Type: UtException
-What: Invalid duplicate of message to transmit encountered for WsfCommMediumGuided.
-Stacktrace:
-     0# 0x7ffcf45d3dc6 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     1# 0x7ffcf463d193 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     2# 0x7ffcf463cb11 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     3# 0x7ffcf45bc9b4 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     4# 0x7ffcf4681a67 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     5# 0x7ffcf458d898 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     6# 0x7ffcf45be023 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     7# 0x7ffcf4f44f17 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     8# 0x7ffcf4f44e72 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-     9# 0x7ffcf4f43feb (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-    10# 0x7ffcf4f57b90 (WsfExtEntityDeadReckon::WsfExtEntityDeadReckon) at ??
-    11# 0x7ffd2a68d090 (warlock::net::ListBase::ListBase) at ??
-    12# 0x7ffcf733eaa0 (QThread::start) at ??
-    13# 0x7ffd66e97374 (BaseThreadInitThunk) at ??
-    14# 0x7ffd687dcc91 (RtlUserThreadStart) at ??
-
-