Netlogo: calculate turtle variable for different patch types

By -

I'm trying to calculate a turtle variable (district-winner) for every value of a certain patch variable (district). Patch "district" ranges from 0 to 100. The patches are also endowed with a feature votes. The turtle (called party in the code) receives a patches' votes if it is the closest turtle to that patch. For every patch district I wish to indicate the turtle that receives most votes in that particular patch district, and stall the information in some variable (e.g. district-vote or district-winner). That is where I got stuck.

I have tried working with "foreach" and "sort-by", but so far I haven't managed to create a code without error that accounts for every different district value. The code for assigning votes to some closest turtle works (see code). But I haven't figured out how to calculate the votes won by turtles per district for each district.

Do you know how to create a turtle variable that is conditionalised on some patch variable value?

Any help would be much appreciated!

Working code, relevant lines:

to update-support
  ask patches [set closest-party min-one-of parties [distance myself]]
      ;;patches find their closest party
  ask parties [set mysize sum [votes] of patches with [closest-party = myself]] 
      ;;each party sums the votes on patches for which it is the closest party    
end

Some attempt to run the code for different patch districts:

to update support
 ask patches [
   set closest-party min-one-of parties [distance myself]
     ;;patches find their closest party
   set closest-party-list [ (list closest-party) ] of patches
      (foreach district-number
        [set district-vote-map map [ifelse-value (? != district) [? = district] [?]] closest- 
        party-list])
   ;;and then link this closest-party-list to some code for asking parties?? 
   ]
  ]
end

Another attempt

to update support
  ask patches [
    set closest-party min-one-of parties [distance myself]]
        ;;patches find their closest party
  ask parties [
    set district-vote [
      (foreach [(district) of patches] sum [votes] of patches with [closest-party = myself] and 
      [district = [?]])]
end


Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more