Autoencoder not learning well when have deeper layers

By -

I am building a deep CNN autoencoder on time series data. When I experiment with different layers, I found something that I can not explain:

  1. when I have more layers, i.e. the encoder bottleneck layer will have smaller dimensions of the kernel and more layers for the decoder layers (because it is symmetric), I found the test performance (MSE) is increasing, the training error increasing as well. I was thinking more layers will have better encoding capability and should decrease the error, but the results are opposite.
  2. Also, when I decrease the dimension of the bottleneck to a certain level (say adding 5 layers to the encoder), the model seems not to learn at all, the validation loss basically is the same from the very first few epoch (only change slightly at the beginning). No matter how many kernels I use, the results are the same. But if I reduce the encoder layers, and make it shallower, it learns without any problem.

My structure of autoencoder is similar to this CNN autoencoder on tensorflow tutorial, with only the difference of adding more layers. Also, I am increasing the number of kernels with deeper layers instead of decreasing as the one shown on their website. Because I was thinking that the deeper the layers, your features are more high-level and specific that you need more kernels to capture them. Does this sound right?

Really hope I can get some suggestions here. Thanks in advance.



from Recent Questions - Stack Overflow https://ift.tt/3hkjgG1
https://ift.tt/eA8V8J

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

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

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").build();     TransportClient client = new P
Read more