windows 10
centos 7
python 3.6.5
VScode
I'm trying OpenPose, finally I commanded this code
[vagrant#localhost tf-pose-estimation]$ python3 run.py --model=mobilenet_thin --resize=432x368 --image=images/p2.jpg
but this doesn't show any windows by matplotlib
I changed backend code
\home\vagrant.local\lib\python3.6\site-packages\matplotlib\mpl-data\matplotlibrc
backend : Agg => backend : TKAgg
[vagrant#localhost tf-pose-estimation]$ python3 run.py --model=mobilenet_thin --resize=432x368 --image=images/p2.jpg
/home/vagrant/.local/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1)
or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_qint8 = np.dtype([("qint8", np.int8, 1)])
/home/vagrant/.local/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1)
or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
_np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/home/vagrant/.local/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1)
---except parts of scripts------
TfPoseEstimator/Openpose/MConv_Stage6_L2_5_pointwise/BatchNorm/FusedBatchNorm
TfPoseEstimator/Openpose/concat_stage7/axis
TfPoseEstimator/Openpose/concat_stage7
WARNING:tensorflow:From /home/vagrant/tf-pose-estimation/tf_pose/estimator.py:341: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.
2019-09-10 12:57:56,417 WARNING From /home/vagrant/tf-pose-estimation/tf_pose/estimator.py:341: The name tf.placeholder is deprecated. Please use tf.compat.v1.placeholder instead.
WARNING:tensorflow:From /home/vagrant/tf-pose-estimation/tf_pose/estimator.py:342: The name tf.image.resize_area is deprecated. Please use tf.compat.v1.image.resize_area instead.
2019-09-10 12:57:56,420 WARNING From /home/vagrant/tf-pose-estimation/tf_pose/estimator.py:342: The name tf.image.resize_area is deprecated. Please use tf.compat.v1.image.resize_area instead.
WARNING:tensorflow:From /home/vagrant/tf-pose-estimation/tf_pose/tensblur/smoother.py:96: The name tf.variable_scope is deprecated. Please use tf.compat.v1.variable_scope instead.
2019-09-10 12:57:56,442 WARNING From /home/vagrant/tf-pose-estimation/tf_pose/tensblur/smoother.py:96: The name tf.variable_scope is deprecated. Please use tf.compat.v1.variable_scope instead.
WARNING:tensorflow:From /home/vagrant/tf-pose-estimation/tf_pose/estimator.py:354: add_dispatch_support..wrapper (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
2019-09-10 12:57:56,463 WARNING From /home/vagrant/tf-pose-estimation/tf_pose/estimator.py:354: add_dispatch_support..wrapper (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
2019-09-10 12:57:56.563567: W tensorflow/compiler/jit/mark_for_compilation_pass.cc:1412] (One-time warning): Not using XLA:CPU for cluster because envvar TF_XLA_FLAGS=--tf_xla_cpu_global_jit was not set. If you want XLA:CPU, either set that envvar,
or use experimental_jit_scope to enable XLA:CPU. To confirm that XLA is active, pass --vmodule=xla_compilation_cache=1 (as a proper command-line flag, not via TF_XLA_FLAGS) or set the envvar XLA_FLAGS=--xla_hlo_profile.
2019-09-10 12:57:57.584627: W tensorflow/core/framework/allocator.cc:107] Allocation of 24164352 exceeds 10% of system memory.
[2019-09-10 12:58:04,331] [TfPoseEstimatorRun] [INFO] inference image: images/p2.jpg in 1.3923 seconds.
2019-09-10 12:58:04,331 INFO inference image: images/p2.jpg in 1.3923 seconds.
Solved it.
Vbox just not on GUI.
Thanks watching.
This teached me how to install GUI on centos7
https://zero-config.com/centos/gnome-0001.html
Related
scheduler | /usr/local/lib/python3.10/dist-packages/airflow/models/base.py:49 MovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings. Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
webserver | /usr/local/lib/python3.10/dist-packages/airflow/models/base.py:49 MovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings. Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
triggerer | /usr/local/lib/python3.10/dist-packages/airflow/models/base.py:49 MovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings. Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
i tried airflow standalone on ec2 instance and error occured
I am getting the below error while using sink_parquet on a LazyFrame. Earlier I was using .collect() on the output of the scan_parquet() to convert the result into a DataFrame but unfortunately it is not working with larger than RAM datasets. Here is the error I received -
PanicException: sink_parquet not yet supported in standard engine. Use 'collect().write_parquet()'
I am trying to write the LazyFrame (the output from scan_parquet) into a local file after I added some filter and join conditions on the LazyFrame.
It seems the error is coming from the below location -
https://github.com/pola-rs/polars/blob/master/py-polars/polars/internals/lazyframe/frame.py#L1235 (In Python)
https://github.com/pola-rs/polars/blob/master/polars/polars-lazy/src/physical_plan/planner/lp.rs#L154 (In Rust) .
I have tried updating to the latest version 0.15.16 0.16.1 but this issue still exists .
Sample code :
pl.scan_parquet("path/to/file1.parquet")
.select([
pl.col("col2"),
pl.col("col2").apply( lambda x : ...)
.alias("splited_levels"),
..followed by more columns and .alias()
])
.join(<another lazyframe>,on="some key",how="inner")
.filter(...)
.filter(..)
..followed by some more filters
.sink_parquet("path/to/result2.parquet")
The parquet file should be written in local system. Instead I am getting the below error -
PanicException: sink_parquet not yet supported in standard engine. Use 'collect().write_parquet()'
Here are the details of the installed packages after I used polars.show_versions() -
--- Version info----
Polars : 0.15.16
Index type : UInt32
Platform : Linux-4.15.0-191-generic-x86_64-with-glibc2.28
Python: 3.9.16
[GCC 8.3.0]
--- Optional dependencies---
pyarrow : 11.0.0
pandas : not installed
numpy : 1.24.1
fsspec : 2023.1.0
connectorx : not installed
xlsx2csv : not installed
deltalake: not installed
matplotlib : not installed
Update : I have raised a github issue here for the same and it seems all types of queries are not supported for streaming at this moment . So I am looking for a work around in this case or any alternative way of doing this with polars
https://github.com/pola-rs/polars/issues/6603
I am having a really hard time getting vim-go to play well with golanci-lint.
golint, which was a default linter for go, has been deprecated. Most users now suggest to use revive.
While the default config of vim-go with golint was working, but printing a deprecated message on the status line, if I put revive instead, I only get
vim-go: [golangci-lint] FAIL
Ubuntu 20.04, with 8.1.2269-1ubuntu5
vim-go: v1.25
.vimrc:
let g:go_metalinter_enabled = []
let g:go_metalinter_command = 'golangci-lint'
let g:go_metalinter_autosave = 1
let g:go_metalinter_autosave_enabled = ['vet','revive','errcheck','staticcheck','unused','varcheck']
while trying to start elasticsearch (version 7.9) node, with the following command :
D:\temp\elasticsearch-7.9.2> .\bin\elasticsearch.bat -Ecluster.name=my_cluster -Enode.name=node_2 Epath.data=data
i got the error:
D:\temp\elasticsearch-7.9.2>.\bin\elasticsearch.bat -Ecluster.name=my_cluster -Enode.name=node_2 E node.path.data=data
future versions of Elasticsearch will require Java 11; your Java version from [C:\Program Files\Java\jdk1.8.0_181\jre] does not meet this requirement
future versions of Elasticsearch will require Java 11; your Java version from [C:\Program Files\Java\jdk1.8.0_181\jre] does not meet this requirement
Warning: with JDK 8 on Windows, Elasticsearch may be unable to derive correct
ergonomic settings due to a JDK issue (JDK-8074459). Please use a newer
version of Java.
Warning: MaxDirectMemorySize may have been miscalculated due to JDK-8074459.
Please use a newer version of Java or set MaxDirectMemorySize explicitly.
Starts Elasticsearch
Option Description
------ -----------
-E <KeyValuePair> Configure a setting
-V, --version Prints Elasticsearch version information and exits
-d, --daemonize Starts Elasticsearch in the background
-h, --help Show help
-p, --pidfile <Path> Creates a pid file in the specified path on start
-q, --quiet Turns off standard output/error streams logging in console
-s, --silent Show minimal output
-v, --verbose Show verbose output
ERROR: Positional arguments not allowed, found [E, node.path.data=data]
i missed th dash - in front of the path parameter (i typed: Epath.data=data instead of -Epath.data=data)
once this was addressed the node started
D:\temp\elasticsearch-7.9.2>.\bin\elasticsearch.bat -Ecluster.name=my_cluster -Enode.name=node_2 -Epath.data=data
While reading the docs of System.Process and trying to use callCommand I discovered that it is not available:
test.hs:1:24: Module `System.Process' does not export `callCommand'
Why?
callProcess was added to the process library in version 1.2.0.0. I suspect you are using an earlier version.