Dealer.agent.xml

最新推荐文章于 2023-09-06 19:00:00 发布
最新推荐文章于 2023-09-06 19:00:00 发布
阅读量114 收藏
点赞数
分类专栏： jade 文章标签： XML Access UP
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/iteye_10365/article/details/81898669
版权
<!--
<H3>The blackjack dealer controls the game.</H3>

The dealer registers itself at the DirectoryFacilitator
and waits for player agents to join the table.
-->
<agent xmlns="http://jadex.sourceforge.net/jadex"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jadex.sourceforge.net/jadex
http://jadex.sourceforge.net/jadex-0.96.xsd"
name="Dealer"
package="jadex.examples.blackjack.dealer">

<imports>
<import>jadex.examples.blackjack.*</import>
<import>jadex.examples.blackjack.gui.*</import>
<import>jadex.runtime.*</import>
<import>jadex.planlib.*</import>
<import>jadex.util.*</import>
<import>jadex.adapter.fipa.*</import>
<import>java.util.logging.*</import>
<import>java.util.*</import>
</imports>

<capabilities>
<!-- this capability provides easy access to "out-of-the-box"-plans
allowing - for example - to register at the DF. -->
<capability name="dfcap" file="jadex.planlib.DF"/>
</capabilities>

<!--
These are the dealers beliefs. None of these beliefs should be edited in the ADF
because all beliefs are initialised by the plans during the game or have
expedient start-up values (like the three beliefs below).
-->
<beliefs>
<!-- The card set used to play the game. -->
<belief name="cardset" class="CardSet" />

<!-- The number of seconds to wait for answers from players. -->
<belief name="playerwaitmillis" class="long">
<fact>(Integer)$propertybase.getProperty("standard.timeout")</fact>
</belief>

<!-- The number of seconds to wait before drawing a card.
Can be adjusted in the GUI. -->
<belief name="stepdelay" class="int">
<fact>1</fact>
</belief>

<!-- When set to true, each step in the game must be manually
issued in the GUI. -->
<belief name="singleStepMode" class="boolean">
<fact>false</fact>
</belief>

<!-- The self representation of the dealer. -->
<belief name="myself" class="Dealer">
<fact>new Dealer()</fact>
</belief>

<!-- The players. -->
<beliefset name="players" class="Player"/>

<!-- The history of played games. -->
<belief name="statistics" class="GameStatistics">
<fact>new GameStatistics()</fact>
</belief>

<belief name="gamestate" class="GameState">
<fact>new GameState($beliefbase.myself, null)</fact>
</belief>

<belief name="gui" class="DealerFrame"/>

<!--
It's possible that a few different manager (possibly from remote Players)
want to track their players during the game, therefor a beliefset containing
all manager-AIDs is needed.
-->
<beliefset name="tracker" class="AgentIdentifier"/>

</beliefs>

<!--
The dealer has only one initial goal: registering a
dealing-service at the DF and renew this registration
every 10 seconds.
-->
<goals>
<!-- Main goal to play a game. -->
<performgoal name="play_game" exclude="never" retrydelay="3000">
<contextcondition>
$beliefbase.players.length > 0
</contextcondition>
</performgoal>

<!-- Goal to play with a single player (in the context of a larger game). -->
<performgoal name="play_with_player">
<parameter name="player" class="Player"/>
</performgoal>

<!-- Used for registering the dealer at the df. -->
<achievegoalref name="df_register">
<concrete ref="dfcap.df_register"/>
</achievegoalref>
<!-- Used for deregistering the dealer at the df. -->
<achievegoalref name="df_deregister">
<concrete ref="dfcap.df_deregister"/>
</achievegoalref>
</goals>

<!--
These are all the plans, the dealer will execute during a game.
There is one plan for every major task. Have a look into the
plan-classes to get a detailed insight in whats going on there.
-->
<plans>
<!-- Register a player. -->
<plan name="register_plan">
<body class="DealerRegisterPlayerPlan" />
<!-- <body>new DealerRegisterPlayerPlan()</body>-->
<trigger>
<messageevent ref="request_join" />
</trigger>
</plan>

<!-- Play a game. -->
<plan name="play_game_plan">
<body class="DealerGameRoundMasterPlan" />
<!-- <body>new DealerGameRoundMasterPlan()</body> -->
<trigger>
<goal ref="play_game"/>
</trigger>
</plan>

<!-- Play a game with a single player. -->
<plan name="play_with_player_plan">
<parameter name="player" class="Player">
<goalmapping ref="play_with_player.player"/>
</parameter>
<body class="DealerGameRoundPlayerPlan" />
<!-- <body>new DealerGameRoundPlayerPlan()</body>-->
<trigger>
<goal ref="play_with_player"/>
</trigger>
<!-- <contextcondition>
$beliefbase.getBeliefSet("players").containsFact($plan.player)
&& !$plan.player.getState().equals(Player.STATE_IDLE)
</contextcondition>-->
<contextcondition>
$beliefbase.getBeliefSet("players").containsFact($plan.player)
&& !$plan.player.getState().equals(Player.STATE_IDLE)
</contextcondition>
</plan>

<plan name="propagate_game_state_plan">
<body class="PropagateGameStatePlan" />
<!-- <body>new PropagateGameStatePlan()</body> -->
<trigger>
<beliefchange ref="myself"/>
<beliefsetchange ref="players"/>
</trigger>
<!-- not possible because game must always be updated. -->
<!--<precondition>$beliefbase.players.length>0</precondition>-->
</plan>
</plans>

<!-- events -->
<events>

<!-- Event to trigger a step. -->
<internalevent name="step"/>

<!-- player messages -->
<!-- Player request to join the game. -->
<messageevent name="request_join" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestJoin.class</value>
</parameter>
</messageevent>

<!-- A player wants to draw another card. -->
<messageevent name="request_draw" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestDraw.class</value>
</parameter>
</messageevent>

<!-- A player makes a bet. -->
<messageevent name="request_bet" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<!--<parameter name="reply-with" class="String" direction="inout">
<value>SFipa.createUniqueId($scope.getAgentName())</value>
</parameter>-->
<parameter name="conversation-id" class="String" direction="inout">
<value>SFipa.createUniqueId($scope.getAgentName())</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestBet.class</value>
</parameter>
</messageevent>


<messageevent name="refuse_bet" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REFUSE</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestBet.class</value>
</parameter>
</messageevent>

<!-- A player has finished its game (i.e. doesn't want to draw any more cards). -->
<messageevent name="request_finished" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REQUEST</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>RequestFinished.class</value>
</parameter>
</messageevent>

<!-- todo: manager messages -->

<!-- The manager is shutting down the BlackJack application. -->
<messageevent name="inform_shutdown" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="content-start" class="String" direction="fixed">
<value>"manager:shutDown"</value>
</parameter>
</messageevent>
<!-- The manager registers as tracker on game settings. -->
<messageevent name="query_tracking" direction="receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.QUERY_REF</value>
</parameter>
<parameter name="content-start" class="String" direction="fixed">
<value>"manager:registerAsTracker"</value>
</parameter>
</messageevent>

<!-- sent messages -->

<!-- inform a player about a the game result -->
<messageevent name="inform_action_done" direction="send_receive" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>Done.class</value>
</parameter>
</messageevent>

<!-- inform a player about a the game result -->
<messageevent name="refuse_action" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.REFUSE</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
</messageevent>

<!-- inform tracker about playing players -->
<messageevent name="inform_tracker" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="content" class="String" direction="in" />
</messageevent>

<messageevent name="inform_game_state" direction="send" type="fipa">
<parameter name="performative" class="String" direction="fixed">
<value>SFipa.INFORM</value>
</parameter>
<parameter name="language" class="String" direction="fixed">
<value>SFipa.NUGGETS_XML</value>
</parameter>
<parameter name="ontology" class="String" direction="fixed">
<value>BlackjackOntology.ONTOLOGY_NAME</value>
</parameter>
<parameter name="conversation-id" class="String" direction="inout">
<value>SFipa.createUniqueId($scope.getAgentName())</value>
</parameter>
<parameter name="content-class" class="Class" direction="fixed">
<value>GameState.class</value>
</parameter>
</messageevent>

</events>

<expressions>

<!-- The player that gets the next card (if any). -->
<expression name="turnplayer">
select one Player $p from $beliefbase.players
where $p.getState().equals(Player.STATE_PLAYING)
order by $p.getCards().length
</expression>

<!-- Check if it is the dealer's turn. -->
<condition name="dealers_turn">
// The dealer may draw its initial card when all players have two cards.
$beliefbase.myself.getCards().length==0 &&
(select one Player $p from $beliefbase.players
where !$p.getState().equals(Player.STATE_IDLE) && $p.getCards().length!=2)
== null

// The dealer may draw more cards, when all players are either idle or finished.
|| (select one Player $p from $beliefbase.players
where !$p.getState().equals(Player.STATE_IDLE) && !$p.getState().equals(Player.STATE_FINISHED))
== null
</condition>

<!-- Check if it is the $player's turn. -->
<condition name="players_turn">
// All players must be idle, playing, or finished.
(select one Player $p from $beliefbase.players
where !$p.getState().equals(Player.STATE_IDLE)
&& !$p.getState().equals(Player.STATE_PLAYING)
&& !$p.getState().equals(Player.STATE_FINISHED))
== null

// And this player must be the first with the least number of cards.
// Hack !!! Assume "any" selects players in order.
&& (select one Player $p from $beliefbase.players
where $p.getState().equals(Player.STATE_PLAYING)
&& $p.getCards().length<=$player.getCards().length
order by $p.getCards().length)
== $player
<parameter name="$player" class="Player"/>
</condition>

<!-- Check if the dealer has drawn its first card. -->
<condition name="dealer_card">
$beliefbase.myself.getCards().length==1
</condition>

<!-- Check if the dealer has finished drawing cards. -->
<condition name="dealer_finished">
$beliefbase.myself.getState().equals(Player.STATE_FINISHED)
|| $beliefbase.myself.getState().equals(Player.STATE_IDLE)
</condition>

</expressions>

<properties>
<!-- logging-properties, needed to debug the application.
Start the Jadex-Logging-Agent to see whats going on behind the scenes -->
<!--<property name="logging.level">Level.INFO</property>-->
</properties>

<configurations>
<configuration name="default">
<beliefs>
<initialbelief ref="gui">
<fact>new DealerFrame($beliefbase.myself, $agent.getExternalAccess())</fact>
</initialbelief>
</beliefs>
<goals>
<!-- Register the dealer at the df on startup. -->
<initialgoal ref="df_register">
<!-- The services to register. -->
<parameter ref="description">
<value>
<!-- This is the agent-description for the dealer. With this description
the dealers is registered at the directory facilitator.
Note, that the dealer only offers one service, that is 'dealing'
(see service description below). -->
SFipa.createAgentDescription(null,
SFipa.createServiceDescription("dealing", "blackjack", "University of Hamburg"))
</value>
</parameter>
</initialgoal>
<initialgoal ref="play_game"/>
<endgoal ref="df_deregister"/>
</goals>
</configuration>
</configurations>

</agent>
iteye_10365
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
iLabelChina(Dealer).rar
06-20
电子秤标签格式设置软件iLabelChina(Dealer)2.31i cn版
fastdfs-6.9.5.tar.gz
08-25
git官网版，供无法用git下载的使用，liunx使用。 FastDFS（Fast Distributed File System）是一个开源的轻量级分布式文件系统，主要用于文件存储和访问。它以高性能和高可靠性为目标，特别适用于一些需要大规模文件...
Proxy 和 Agent 区别
热门推荐
木木
05-25 1万+
<br />Agent 代理 通常指与用户接口的客户端程序<br />Proxy 代理 接收用户请求并将请求发给服务器,然后接收服务器回应并返回给用户 实际上Proxy的功能就是代替用户访问服务器,用户被隐藏.
游戏服务端究竟解决了什么问题？
wubaohu1314的博客
09-13 476
https://www.fgba.net/sitemap.xml
springboot的maven多模块项目架构微服务搭建——依赖方式的多模块演化为微服务项目...
zuixiaoyao_001的博客
12-03 3446
在上一篇依赖方式多模块的基础上对项目进行改造。主要改造user-service项目，service要配置mapper。mybatis及数据库相关的东西，后面的接口消费方user就不再需要了 注意：以下代码是在不同场所的机器上写的，数据库什么的会有不同，结构也会有不同，最终的代码会以其中一个传递到本人git上，这里记录的是本人总结的一些思路什么的，稍微修改配置，配置一致，就可以运行的 代码...
企业微信url及生成授权链接
wewewe14的博客
09-13 1万+
企业微信第三方开发课程 14-18 一、简介 这里主要分为四部分，验证 url 有效性、完成用户的测试安装、获取生成预授权码、生成授权安装链接。这几部就可以完成第三方有用的回调和安装，这也是后续功能开发的基础。 二、Get 请求验证 URL 有效性 1.为什么要搭建回调服务 在集成企业微信与内部系统时，搭建一个回调服务可以获取到用户通过企业微信发送给应用的消息： 自定义丰富的服务行为。比如，用户向应用发消息时，识别消息关键词，回复不同的消息内容； 用户点击应用菜单时，转化为指令，执行自动化任务。 可以及时
java List<Map<String,Object>
weixin_30535913的博客
01-03 134
xml <select id="selectShopList" resultType="java.util.HashMap"> SELECT p.PARTY_NAME partyName, c.CUSTOMER_NAME customerName, s.SHOP_ID shopId, s.SHOP_NAME shopNam...
SpringBoot实现小程序微信支付（超级详细）
qq_19007169的博客
03-21 9730
SpringBoot微信支付开发
linux7下nenux3.14的maven私服搭建和配置使用
zuixiaoyao_001的博客
10-27 2498
&#13; 　　为什么用私服，各种帖子很多，话不多说，直接奉上本博主的搭建过程。 　　一、环境准备：确保jdk和maven安装完成 　　二、下载nenux；地址：https://www.sonatype.com/download-oss-sonatype?hsCtaTracking=920dd7b5-7ef3-47fe-9600-10fecad8aa32%7Cf59d5f1...
python模块之 aiomysql 异步mysql
最新发布
局外人LZ的博客
09-06 2468
aiomysql 是一个基于 asyncio 的异步 MySQL 客户端库，用于在 Python 中与 MySQL 数据库进行交互。它提供了异步的数据库连接和查询操作，适用于异步编程环境异步支持：aiomysql 是基于 asyncio 实现的，可以与 asyncio 框架无缝集成，充分利用异步编程的优势，提高应用程序的性能和并发能力。高性能：aiomysql 使用了底层的 PyMySQL 库，通过异步操作和连接池技术，可以实现高性能的数据库访问。
mysql服务异常中止_数据库服务异常停止分析
weixin_39612554的博客
01-27 1067
sqlserver数据库服务异常停止分析背景2019年11月13日早上9:37分钟，我们的运维监控系统告警提示某项目数据库服务1433端口无法访问，我们赶紧登陆服务器查看详情，发现数据库服务以及数据库agent服务都已停止，重新手工启动对应的服务恢复生产。接下来我们就需赶紧分析引起这个问题的原因以及如何去修复；服务器环境情况如下：Microsoft SQL Server 2017 (RTM-CU1...
Python库 | dealer-1.0.1.tar.gz
05-14
资源分类：Python库 所属语言：Python 资源全名：dealer-1.0.1.tar.gz 资源来源：官方 安装方法：https://lanzao.blog.csdn.net/article/details/101784059
施乐DocuPrint P M105 205 158 维修手册（Dealer）.pdf
09-21
施乐DocuPrint P M105 205 158 维修手册（Dealer）.pdf
caufieldpeterj.github.io
02-09
==============================================黑杰克假密码游戏名称：... const Dealer = {};/ *第一种方法//创建deckOfCards对象，其中西装是钥匙，值是纸牌值let deckOfCards = {俱乐部：[2,3,4,5,6,7,8,9,10,10,1
zotero与word集成
图灵门徒
09-11 761
Manually Installing the Zotero Word Plugin for Windows To install the plugin by hand, first download the plugin: * Install the Word Plugin for Windows for Zotero 2.0 Once the plugi...
society of mind
图灵门徒
08-08 609
To appear in the journal Computing and Informatics. Examining the Society of Mind Push Singh 28 October 2003 push@mit.edu Media Lab Massachusetts Institute of Technology 20 Ames Street C...
booktrading / common
图灵门徒
03-29 482
&lt;html&gt;&lt;head&gt;&lt;title&gt; jadex.examples.booktrading.common &lt;/title&gt;&lt;/head&gt;&lt;body&gt; This package contains classes used by buyer and seller agents of thebooktrading scenar...
Snowball分词
图灵门徒
08-22 401
using System; using Lucene.Net.Analysis; using Lucene.Net.Analysis.Standard; using SF.Snowball.Ext; using System.Collections.Generic; using System.Collections; using OpenNLP.Tools.PosTagger; ...
springboot zmq dealer
08-31
在给出的代码中，Spring Boot应用程序使用了ZeroMQ（简称ZMQ）来实现与一个Dealer连接的功能。Dealer是ZeroMQ模式中的一种角色，它代表一个消息的接收者和发送者。 首先，代码中的`@Value("${spring.zeromq.enable}...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值