You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, it seems that there is a problem about the arguments related to matplotlib-v.2.2.3.
I am attempting to test the E1 example with SCHISM-v.1.1.2. After modifying the absolute path in E1.yaml. I run the following command as Usage Examples manual:
$ runSchism analyze --config E1.yaml
but it returns warnings:
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/bin/runSchism", line 155, in<module>main()
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/bin/runSchism", line 152, in main
args.func(args)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/bin/runSchism", line 137, in run_schism
plot_mut_clust_cellularity(args)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/SCHISM/visualize.py", line 530, in plot_mut_clust_cellularity
alpha = 0.5)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/__init__.py", line 1867, in inner
return func(ax, *args, **kwargs)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/axes/_axes.py", line 5165, in fill_between
collection = mcoll.PolyCollection(polys, **kwargs)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/collections.py", line 961, in __init__
Collection.__init__(self, **kwargs)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/collections.py", line 170, in __init__
self.update(kwargs)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/artist.py", line 888, in update
fork, vinprops.items()]
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/artist.py", line 882, in _update_property
return func(v)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/collections.py", line 677, in set_color
self.set_facecolor(c)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/collections.py", line 705, in set_facecolor
self._set_facecolor(c)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/collections.py", line 690, in _set_facecolor
self._facecolors = mcolors.to_rgba_array(c, self._alpha)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/colors.py", line 267, in to_rgba_array
result[i] = to_rgba(cc, alpha)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/colors.py", line 168, in to_rgba
rgba = _to_rgba_no_colorcycle(c, alpha)
File "/home/ninomoriaty/anaconda3/envs/EvolCancer/lib/python2.7/site-packages/matplotlib/colors.py", line 212, in _to_rgba_no_colorcycle
raise ValueError("Invalid RGBA argument: {!r}".format(orig_c))
ValueError: Invalid RGBA argument: 'f'
And it returns the following output documents : 0_E1_result.cluster.cellularity, 0_E1_result.HT.cpov, 0_E1_result.HT.cpov.pdf, 0_E1_result.HT.pov, 0_E1_result.HT.pvalues, 0_E1_result.mutation.cellularity.
It seems that the problem is caused by the arguments which conflict with matplotlib-2.2.3. But I am not sure about how to deal with it. And that is why I am writing an issue for some recommendation and advice.
The text was updated successfully, but these errors were encountered:
Hello, it seems that there is a problem about the arguments related to matplotlib-v.2.2.3.
I am attempting to test the E1 example with SCHISM-v.1.1.2. After modifying the absolute path in E1.yaml. I run the following command as Usage Examples manual:
but it returns warnings:
And it returns the following output documents : 0_E1_result.cluster.cellularity, 0_E1_result.HT.cpov, 0_E1_result.HT.cpov.pdf, 0_E1_result.HT.pov, 0_E1_result.HT.pvalues, 0_E1_result.mutation.cellularity.
It seems that the problem is caused by the arguments which conflict with matplotlib-2.2.3. But I am not sure about how to deal with it. And that is why I am writing an issue for some recommendation and advice.
The text was updated successfully, but these errors were encountered: