python - Why are the heatmap color values appearing as thin rectangular strips instead of squares? -


this question exact duplicate of:

how can improve appearance of heatmap? why color values appearing thin rectangular strips (with white space in between) instead of squares or happens depending on data file? not heatmap supposed like.

heatmap

data

import numpy np import pandas pd import matplotlib.pyplot plt import seaborn sns sns.set(color_codes=true) np.random.seed(sum(map(ord, "distributions")))  data = pd.read_csv('dvang_heatmap.dat',sep='\s',engine='python') data2 = pd.pivot_table(data.round(2),values='k',index='g',columns='h')  mask = np.isnan(data2)  sns.set(style="white")  xtics = 20 ytics = 10 cmap = "jet" vmin = none vmax = none  ax = sns.heatmap(data2, xticklabels=xtics, yticklabels=ytics, mask=mask, linewidths=0, cbar=true, robust=false,cmap=cmap, vmin=vmin, vmax=vmax)  ax.invert_yaxis()  plt.title('heatmap') plt.xlabel('angle') plt.ylabel('separation')  plt.savefig('heatmap.png', transparent=true)  sns.plt.show()

read documentation. have add square=true keyword. default, option set false.

under hood, seaborn calling matplotlib.pyplot.imshow , using square keyword sets axes.set_aspect('equal'). if using square=true has extreme of effect, can try setting aspect manually: ax.set_aspect(num) num number describing height:width ratio of resulting rectangles.


-

Popular posts from this blog

node.js - How do I prevent MongoDB replica set from querying the primary? -

read-operations-only: is there way have mongodb replica set, make mongodb instance on box connected to, mongodb gets queried? i have 3 ec2 instances behind aws load balancer. on each ec2 instance runs mongodb, part of replica set. i have express endpoints on nodejs , connect replica set follows mongodb.mongoclient.connect('mongodb://1.1.1.1,2.2.2.2,3.3.3.3.', function (err, db) { if (err) { complete('{}'); } else { i distribute load of queries evenly across 3 instances of mongodb replica set instead of default having queries routed ec2 instance primary mongodb defined, because destroys point of load balancer (which balance load of queries across 3 instances evenly). my understanding when connecting mongodb replica set, primary instance selected unless primary instance down, , therefore purpose of every secondary instance serve backup. in example people call hot,cold,cold. because there 2...
Read more

Apache NiFi ExecuteScript: Groovy script to replace Json values via a mapping file -

i working apache nifi 0.5.1 on groovy script replace incoming json values ones contained in mapping file. mapping file looks (it simple .txt): header1;header2;header3 a;some text;a2 i have started following: import groovy.json.jsonbuilder import groovy.json.jsonslurper import java.nio.charset.standardcharsets def flowfile = session.get(); if (flowfile == null) { return; } flowfile = session.write(flowfile, { inputstream, outputstream -> def content = """ { "field1": "a" "field2": "a", "field3": "a" }""" def slurped = new jsonslurper().parsetext(content) def builder = new jsonbuilder(slurped) builder.content.field1 = "a" builder.content.field2 = "some text" builder.content.field3 = "a2" outputstream.write(builder.toprettystring().ge...
Read more