# local state file + remote data + pv-visualizer
**URL:** https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636
**Category:** Web Support
**Created:** [May 16, 2022, 1:21pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636 "2022-05-16T13:21:19Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@parismulye](https://discourse.paraview.org/u/parismulye)
#### Post date: [May 16, 2022, 1:21pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636/1 "2022-05-16T13:21:19Z")
Hello,
I am trying to load a state file (stroed locally) and it is referring to the data on the server (remote) using pv-visualizer. Any ideas as to how to do it?
Some additional points to make:
- Why I am doing like this: ([Loading State file in Paraview Client - #2 by wascott](https://discourse.paraview.org/t/loading-state-file-in-paraview-client/1548/2))
- This works fine with the paraview (but not with visualizer)
- I tried giving multiple paths (one local and one remote) in the --data argument as follows:
–data ‘data1=remotepath|data2=localpath’ but this does not work either.
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [May 16, 2022, 3:49pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636/2 "2022-05-16T15:49:55Z")
In visualizer the purpose of `--data` is really to limit server side data browsing. In fact the Python code that execute on the server can only see the server side. If you want to read a local file, you will have to use the browser file dialog to browse your local files. And then send it to the server for processing. But to achieve that part, you will have to extend the web application logic.
Hope that make sense,
Seb
---
### Author:  [@parismulye](https://discourse.paraview.org/u/parismulye)
#### Post date: [May 16, 2022, 4:56pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636/3 "2022-05-16T16:56:10Z")
Thanks Sebastien for such a quick and precise reply.
Based on your comment, what worked for me is the following:
What worked for me is (and I do this because I want to automate as much as possible):
- `--load-file` [local state-file path and name]
- Didn’t use `--data` (as the remote files that I wanted to open/process were already referenced inside the local state file)
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [May 16, 2022, 5:09pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636/4 "2022-05-16T17:09:10Z")
In that case, you state file is still on the server, not on the client. 😉
It works for you because you run it locally.
---
### Author:  [@parismulye](https://discourse.paraview.org/u/parismulye)
#### Post date: [May 18, 2022, 1:39pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636/5 "2022-05-18T13:39:34Z")
Yes, but what I have is a three way system:
A client: accesses the website where paraview visualizer is hosted
A website: backend of the website
A remote: this is where the calculation/visualization happens.
A client accesses just the website basically, where it can click on different buttons on the webpage and on the back end of the website, it will do some tasks (based on python flask such as launching a new paraview web visualizer session).
Referring to the above nomenclature, the statefiles are stored on the “website server” but the xdmf/visualization files are stored on the “remote”
---
### Author:  [@jourdain](https://discourse.paraview.org/u/jourdain)
#### Post date: [May 18, 2022, 8:04pm UTC](https://discourse.paraview.org/t/local-state-file-remote-data-pv-visualizer/9636/6 "2022-05-18T20:04:28Z")
I see, that make sense as you are using pvpython@website and pvserver@remote rather than running pvpython@remote directly and doing ws proxy from website to remote.